No longer use RID in secondary progress tracking

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Major - P3
    • 2.8.0-rc0
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      After SERVER-15564, replica set members no longer need to use RID to track secondary progress. Rather, they can use the (config version, id) pair to identify which element of the secondary progress table to update. If the config version transmitted does not match the receiving node's config version, it can simply ignore that update, and expect to extract the information from a subsequent replSetHeartbeat from the node.

            Assignee:
            Spencer Brody (Inactive)
            Reporter:
            Andy Schwerin
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: