-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Replication
-
Fully Compatible
-
Repl 2023-11-27, Repl 2023-12-11
-
5
For majority write concern, in addition to waiting for the committed snapshot to advance past the write, it also waits for a majority of nodes to have their lasDurable (j: true) or lastApplied (j: false) to advance past the write. In fact waiting for the committed snapshot is sufficient in most cases and so the additional wait is usually a no-op and only needed when writeConcernMajorityJournalDefault is false and j: true. We can change it to only perform the additional wait in that particular case.
We can also remove the wait for drop pending collections step as part of waiting for majority since that's no longer necessary today.
- is depended on by
-
-
- Closed
-
- is duplicated by
-
SERVER-83595 Collection drop doesn't need to wait behind drop-pending collection reaper anymore
-
- Closed
-
- is related to
-
-
- Closed
-
- related to
-
-
- Closed
-