-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
ALL
SERVER-65531 describes an issue with malformed oplog entries involving "needsRetryImage" being given to the applyOps command.
max.hirschhorn@mongodb.com discovered a corner case that can generate an oplog entry with "needsRetryImage" involving passing a findAndModify oplog entry through the applyOps command. This generates an oplog entry without lsid, txnNumber, and needsRetryImage and as a result secondaries won't update their config.image_collection entry.
We've decided to file this issue as a separate ticket as we believe it's not necessarily resolved by SERVER-65531, whose resolution may simply involve writing to config.image_collection if lsid and txnNumber exist.
- is related to
-
SERVER-65531 Crash when running applyOps command with "needsRetryImage" option
- Backlog
-
SERVER-33326 Remove use of applyOps/doTxn from sharding chunk operations
- Closed
-
SERVER-33182 Remove atomic applyOps
- Closed