-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
Repl 2017-03-27
-
0
Implicit collection creation is never correct during initial sync. In index builds we call getOrCreateCollection which creates the collection to index if we don't have one.
Additionally, we do not call txn->setReplicatedWrites(false) on the operation context created for background index builds, so when those create a new collection, they also attempt to write to the oplog. This behavior should probably be changed, but the real problem is the implicit collection creation.
- depends on
-
SERVER-24927 Ignore NamespaceNotFound errors during initial sync apply ops, because they are transient
- Closed
- is related to
-
SERVER-21583 ApplyOps background index creation may deadlock
- Closed
-
SERVER-16274 secondary fasserts trying to replicate an index
- Closed
-
SERVER-14860 Make background index building work again
- Closed
-
SERVER-16943 Add test for compatibility of replset background index and renameCollection
- Closed
-
SERVER-27205 Remove implicit collection creation from SyncTail
- Closed
-
SERVER-17634 do not apply replicated insert operations on missing collections
- Closed