Accounting for data not capture by ChangeStream

Hello Community,

How do you account for data not captured by ChangeStream. May be for whatever reason before the Change Stream is unable captures the oplog data before it gets overwritten. Is there way to validate whatever DML operations currently captured by ChangeStream reflects the true positions the DML operations in its entirety.

Your response is greatly appreciated.

Hi @Samson_Eromonsei,

Welcome to MongoDB Community.

The change streams events for majority acknowledge data is streamed consistently and in case of a failure or an invalidation may be resumed based on the resume token provided or the last successful cluster time known:

All the above is sufficient if the resume point can be located in the Oplog window available on the Primary. Therefore make sure your oplog has a sufficient time to avoid a possibility of unrecoverable gap of events and a hard restart of the change stream.

Please let me know if you have any additional questions.

Best regards,

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.