-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 2.0.2
-
Component/s: Replication
-
None
-
ALL
When you call rs.remove(), the removed node still looks a lot like a replica set.
- It still responds to rs.status().
- It claims to be syncing from a node in the original replica set.
- It has a state of STARTUP.
- It has the same name as the old replica set.
To avoid confusion on the client side, removed nodes should immediately terminate.
- is related to
-
SERVER-5058 mongos should update config seed based on rs version
- Closed