You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are evaluating mongodb_consistent_backup. I'm trying to understand how the program stores oplog changes. We are using sharded replica set. I'm checking the logs for config replica backup and I'm seeing something like:
Done tailing oplog on configRepl/10.xx.xx.xx:27019, 16010 oplog changes, end ts: Timestamp(1523625054, 1)
But the last document in configRepl.tar/dump/oplog.bson has timestamp 1523625034, so it would appear oplog dump ends 20 secs earlier. I did a:
Hi,
We are evaluating mongodb_consistent_backup. I'm trying to understand how the program stores oplog changes. We are using sharded replica set. I'm checking the logs for config replica backup and I'm seeing something like:
Done tailing oplog on configRepl/10.xx.xx.xx:27019, 16010 oplog changes, end ts: Timestamp(1523625054, 1)
But the last document in configRepl.tar/dump/oplog.bson has timestamp 1523625034, so it would appear oplog dump ends 20 secs earlier. I did a:
and it would appear it's missing around 22 entries.
I am reading the statistics correctly?
The text was updated successfully, but these errors were encountered: