-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
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.
- depends on
-
SERVER-15564 Include config version and member id when sending replSetUpdatePosition messages
- Closed
- is related to
-
SERVER-15444 Clean op old entries in the slave tracking map
- Closed
-
SERVER-15082 Make sure that handshake is always sent before replSetUpdatePosition
- Closed
-
SERVER-15698 Remove support for RIDs in slave tracking
- Closed
-
SERVER-14687 Make sure replset config version matches when processing replication handshakes
- Closed
- related to
-
SERVER-14424 RID is not a sufficiently unique identifier
- Closed