Redundancy where source data on primary is deleted and replaced regularly

Working with Data
1

Hi,

We have a simple P-S-S configuration and an use case where our source data which comes from a third party pipeline, removes the existing data and replaces it on the primary.

Our secondary servers immediately replicates the data, but the functionality we want is redundancy. While our primary is being updated with data (deletion and insertion) , we want the secondaries to have the old data available for clients.

Is this possible on our config?

1 Like
2

May be this can help https://docs.mongodb.com/manual/core/replica-set-delayed-member/

2 Likes