-
Type: Task
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Replication
Once we are allowed to do PIT reads on secondaries that fall in the middle of previous secondary application batches, we'll be able to get rid of ReplicationCoordinatorImpl::_stableOpTimeCandidates. At that point the stable timestamp can simply be the min of the lastApplied optime on this node and the replication majority commit point.
- depends on
-
SERVER-34489 Enable new format Unique Index via FCV
- Closed
- is related to
-
SERVER-35344 Stable timestamp and _currentCommittedSnapshot are redundant
- Backlog
-
SERVER-35714 Recover to common point on rollback instead of stable timestamp
- Backlog