[SERVER-4443] FATAL when adding and removing a node. Created: 06/Dec/11 Updated: 29/Feb/12 Resolved: 06/Dec/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.0.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kyle Banker | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
MongoDB v2.0.1 |
||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
Create a three-node replica set with nodes a localhost:30000, localhost:30001, and localhost:30002. Run: rs.remove("localhost:30001") Wait for steady state, then: rs.add("localhost:30001") This is what you get: Tue Dec 6 14:18:42 [rsMgr] replSet error unexpected exception in haveNewConfig() : 0 assertion db/repl/rs.cpp:440 I've been told by Kristina that the issue here is that you must keep the _id the same when you re-add the node at localhost:30001. If that's the case, then the error message in the logs should indicate it. But I'm not sure why this should even be required in the first place. Why would a user of MongoDB have to remember something like that? |