-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.2.1
-
Component/s: Replication
-
Fully Compatible
-
ALL
-
Repl 2016-11-21
-
0
Several users have reported crashes with the message "[repl writer worker 10] writer worker caught exception: :: caused by :: 26 Failed to apply insert due to missing collection" when replicating a write.
This is likely fallout related to the changes from SERVER-17634 that went into 3.2, which enforced the rule that the primary must replicate the createCollection commands whenever a collection is created (explicit or not); When this was not done, it was a bug.
- is related to
-
SERVER-26741 "Fatal Assertion 16360" triggered by temporary collections dropped when restarted in standalone mode
- Closed
- related to
-
SERVER-19768 Failed applyOps command does not create an oplog entry even with some successful writes
- Closed
-
SERVER-17634 do not apply replicated insert operations on missing collections
- Closed