-
Type: Bug
-
Resolution: Works as Designed
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Execution
-
ALL
-
By design, atomic applyOps does not generate a change stream pre-image (kApplyOpsCmd is excluded here). However, the secondaries replicate the applyOps statements without knowing whether they originated from an applyOps command, and they generate a change stream pre-image. This can result in replica set inconsistencies, as the secondaries may hold content in config.system.preimages that is not existent on the primary.
- is related to
-
SERVER-33326 Remove use of applyOps/doTxn from sharding chunk operations
- Closed
-
SERVER-33182 Remove atomic applyOps
- Closed
- related to
-
SERVER-65531 Crash when running applyOps command with "needsRetryImage" option
- Backlog