[SERVER-21687] ReplicaSet configuration info differs among members after dropping & adding members Created: 27/Nov/15 Updated: 14/Apr/16 Resolved: 27/Nov/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.0.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Yang | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | Windows |
| Participants: |
| Description |
|
I setup a MongoDB replicaset. At the beggining, due to limited hardware, I created three MongoDB instances in one server and different ports, then add the three instances into one replicaset. Subsequently, I got an arbiter server, so I added the arbiter into the replicaset and then dropped one instance. Lastly, I got another server which I configured as a normal MongoDB data instance, so I added it into the replicaset and dropped another instance sitting on the first server from the replicaset. Now, I realise I have good replicaset config information in both data node, but not the arbiter server. The arbiter server is still showing the very first replicaset config in which members 3 instance in one same server. I tried various ways to change the replicaset config information in the arbiter server but all in vain. How do I fix this? |
| Comments |
| Comment by Stennie Steneker (Inactive) [ 27/Nov/15 ] |
|
Hi, The SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related community support discussion please post on the mongodb-user group (http://groups.google.com/group/mongodb-user) or Stack Overflow. See our Technical Support page for additional support resources. Thanks, |