-
Type:
Task
-
Status: Closed
-
Priority:
Major - P3
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: Replication
-
Labels:
-
Backwards Compatibility:Fully Compatible
-
Backport Requested:v4.0, v3.6, v3.4
-
Sprint:Repl 2018-11-05, Repl 2018-11-19, Repl 2018-12-03, Repl 2018-12-17
-
Case:
As a sanity check in case a user manually modifies their local database in a way that puts them into this state
- is related to
-
SERVER-38366 Replica set nodes update the term without verifying the config version can lead to unnecessary stepdown.
-
- Closed
-
-
SERVER-38504 On Primary, to verify that our lastAppliedOpTime is lagged behind the TopologyCoordinator::_lastCommittedOpTime, we should compare both its term and timestamp for pv1.
-
- Closed
-
-
SERVER-38505 For pv1, to determine if the oplog entries are applied out of order, we should compare both the term and timestamp of firstOpTimeInBatch and lastAppliedOpTimeAtStartOfBatch
-
- Closed
-