-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
Fully Compatible
-
v4.4
-
Repl 2020-05-04
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
After a reconfig, we drop snapshots, since the definition of majority-committed can change. However, all this does is set _currentCommittedSnapshot to none. It does not change the
_lastCommittedOpTimeAndWallTime in the TopologyCoordinator. This means that the next time we set _currentCommittedSnapshot, either due to the JournalFlusher or replSetUpdatePosition, we will refuse to set _lastCommittedOpTimeAndWallTime backward, so _currentCommittedSnapshot can be set to its previous value from before the reconfig. This means that dropping snapshots after reconfig doesn’t accomplish anything.
The safe reconfig protocol guarantees that operations committed in the old config will never roll back, so we can stop dropping snapshots after a safe reconfig that does not change writeConcernMajorityJournalDefault.
- is depended on by
-
SERVER-47142 Check primary before writing replset config and no-op
-
- Closed
-
- is related to
-
-
- Backlog
-
- related to
-
-
- Closed
-
-
-
- Closed
-
-
SERVER-40649 Drop snapshots for reconfig via heartbeat.
-
- Backlog
-
-
-
- Closed
-