Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-26990

Unify tracking of secondary state between replication and topology coordinators

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.5.8
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • Repl 2017-03-27, Repl 2017-04-17, Repl 2017-05-08, Repl 2017-05-29
    • 0

      ReplicationCoordinatorImpl::_slaveInfo and TopologyCoordinatorImpl::_hbdata contain a lot of duplicate information, and keeping that state separate prevents certain events from being triggered when information comes in via heartbeats or via replSetUpdatePosition. We should push all this information down into the TopologyCoordinator and use it as the single source of information for making decisions about secondary state and replication progress.

            Assignee:
            Unassigned Unassigned
            Reporter:
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: