Non-atomic applyOps commands should not suppress normal oplog generation and then record a single applyOps command in the oplog, but instead log the individual commands.
- is duplicated by
-
SERVER-19768 Failed applyOps command does not create an oplog entry even with some successful writes
- Closed
- related to
-
SERVER-36944 applyOps does not permit unknown field names when creating a v:1 index
- Closed
-
SERVER-37333 [3.4] applyOps does not validate background index spec for system.indexes inserts
- Closed
-
SERVER-29802 Non-atomic applyOps command should not take out a global exclusive lock
- Closed