[SERVER-4344] Re-adding former replica set member has to have same _id Created: 21/Nov/11  Updated: 15/Feb/13  Resolved: 18/Sep/12

Status: Closed
Project: Core Server
Component/s: Replication, Usability
Affects Version/s: 2.0.1
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Tony Hannan Assignee: Kristina Chodorow (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
is duplicated by SERVER-4443 FATAL when adding and removing a node. Closed
Related
related to SERVER-3159 Re-adding member in replica set fails Closed
Operating System: ALL
Participants:

 Description   

Doing rs.remove(HostX) then later rs.add(HostX) does not work if the HostX has not been restarted because its member _id changes. rs.remove(HostX) should really remove so rs.add(HostX) behaves as if it is new.

Some users have been running into this problem. See linked tickets.



 Comments   
Comment by Tony Hannan [ 21/Nov/11 ]

Not necessarily in short succession.

Comment by Scott Hernandez (Inactive) [ 21/Nov/11 ]

Why would you remove and add the member back in short succession?

Generated at Thu Feb 08 03:05:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.