-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
ALL
For example, suppose the primary has a unique index on x. The primary has a document {_id:1, x:4}, deletes this document, and {_id:10000000, x:4} is inserted. In the meantime, a clone is happening, so the secondary clones {_id:1, x:4} before the delete happens, then {_id:10000000, x:4} at the end of the clone. Then it tries to build a unique index on x, which fails, because there are two docs with x:4.
- depends on
-
SERVER-3160 replication initial sync should use the fast compact command code to build indexes
- Closed
- is related to
-
SERVER-4174 Replicaset resync skips building of _id index in certain circumstances
- Closed
- related to
-
SERVER-5840 Error on failed index build during initial-sync results in warning message, not exception (or retry)
- Closed
-
SERVER-5963 exception cloning object in replset7.js
- Closed