Details
-
Bug
-
Resolution: Done
-
Minor - P4
-
None
-
None
-
None
-
*Location*: https://docs.mongodb.com/manual/core/replica-set-oplog/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36
*Referrer*: https://docs.mongodb.com/manual/core/replica-set-arbiter/
*Screen Resolution*: 1920 x 1080
*Location*: https://docs.mongodb.com/manual/core/replica-set-oplog/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36 *Referrer*: https://docs.mongodb.com/manual/core/replica-set-arbiter/ *Screen Resolution*: 1920 x 1080
-
0.25
Description
This section looks like a non-sequitur.
For proper replication operations, entries in the oplog must be idempotent:
initial sync
post-rollback catch-up
sharding chunk migrations