-
Type: Improvement
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
None
We maintain a map of RIDs to their oplog progress which we use when generating replSetUpdatePosition commands to update our upstream sync source. We don't currently clear that map on reconfig, which means if a node is removed then every time we send a replSetUpdatePosition command it will include an entry for the last known optime of the removed node, forever. Instead, we should clear the map on reconfigs and trigger a new handshake and replSetUpdatePosition command upstream, so everyone has an up-to-date view of the progress of the members in the set, and just the members still in the set.
- related to
-
SERVER-15425 Make new replication code resilient to members being removed from the replset config
- Closed