[SERVER-19366] Not able to add a node to cluster Created: 11/Jul/15 Updated: 13/Jul/15 Resolved: 13/Jul/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Varun | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
When I am trying to add a node to the cluster we are getting the below error. Please let me know for any further information qa_1:PRIMARY> rs.add("n7vgq1mhddbmgd02.general.disney.private:10001"); |
| Comments |
| Comment by Sam Kleinman (Inactive) [ 13/Jul/15 ] | |||||||||||||||||||||||||||||||
|
Have you been able to reproduce this error? The error you encountered was in the mongo shell, so you may be able to get around it by using a different client (i.e. driver) or a more recent version of the shell. MongoDB 3.0 includes more strict enforcement of replica set configurations notes, although its unclear from the current state of the cluster if the replica set configuration was previously invalid. You may have better luck attempting to resync the secondary nodes using this procedure which might help you cleanly add them to the set. I hope this helps. For now, I'm going to go ahead and close this ticket: the SERVER project is for bugs and feature requests with the core MongoDB software. For questions and support with your MongoDB deployment consider contacting the mongodb-users group Regards, | |||||||||||||||||||||||||||||||
| Comment by Varun [ 13/Jul/15 ] | |||||||||||||||||||||||||||||||
|
Sam, MongoDB version for all replica sets: 2.4.12 n7vgq1mhddbmgd03.general is primary and below are the outputs of rs.conf() & rs.status()
Previously we had 02 & 01 nodes shown in the cluster having its "stateStr" : "RECOVERY" so we tried to remove the members and add back to the cluster and the mentioned error is seen while adding members. | |||||||||||||||||||||||||||||||
| Comment by Sam Kleinman (Inactive) [ 11/Jul/15 ] | |||||||||||||||||||||||||||||||
|
Hello, Sorry that you have run into this issue. Could you please answer the following questions about your deployment:
Regards, |