Details
-
Bug
-
Resolution: Done
-
Major - P3
-
None
-
None
-
ALL
Description
Currently we keep entries in the slave tracking map forever, even across reconfigs and node removals. We should have some mechanism for cleaning up old, no longer relevant entries.
Attachments
Issue Links
- related to
-
SERVER-15425 Make new replication code resilient to members being removed from the replset config
-
- Closed
-
-
SERVER-15443 Provide mechanism for inspecting the slave tracking map
-
- Closed
-
-
SERVER-15427 Add command to manage the slave map
-
- Backlog
-
-
SERVER-15565 No longer use RID in secondary progress tracking
-
- Closed
-