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

No longer use RID in secondary progress tracking

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 2.8.0-rc0
    • Affects Version/s: None
    • Component/s: Replication
    • 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@mongodb.com Spencer Brody (Inactive)
            Reporter:
            schwerin@mongodb.com Andy Schwerin
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: