Remove stable optime candidates list from ReplicationCoordinator

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Replication
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              [DO NOT USE] Backlog - Replication Team
              Reporter:
              Spencer Brody (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: