-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing oplog entries? #258
Labels
Comments
OK, so the Resolver trims the oplogs to max_ts. I see that. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: