-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Fully Compatible
-
ALL
-
Storage Execution 2025-11-24
-
0
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Similar to SERVER-114164, awaitReplication only guarantees that the secondary's lastApplied opTime is caught up with the primary but not the lastCommittedOpTime. If we want all the writes from the primary to be durable on the secondaries we should use awaitLastOpCommitted to ensure the node has all expected writes when restarted as standalone.
- is related to
-
SERVER-114164 Replace awaitReplication with awaitLastOpCommitted in long_secondary_reads.js
-
- Open
-