-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
Fully Compatible
-
ALL
-
-
Repl 2019-03-25, Repl 2019-04-08, Repl 2019-04-22
-
59
https://github.com/mongodb/mongo/commit/4f858c52b05ecc49d2ae19bbaf59fc0aad445b7e started enqueuing the first document the OplogFetcher returned instead of skipping it. When the OplogFetcher retries its oplog query, if it has enqueued any documents (so not if it's retrying the very first query before enqueuing anything successfully), then this will cause it to duplicate a document and hit an invariant.
- is related to
-
SERVER-36489 Start initial sync oplog fetching from the 'oldest active transaction timestamp'
- Closed
-
SERVER-36490 Initial sync should not actually prepare transactions on applying 'prepareTransaction' oplog entries
- Closed
-
SERVER-36491 During initial sync 'commitTransaction' oplog entries apply the transaction in the prepare oplog entry in their own batch
- Closed