[SERVER-23840] Declaring bind_ip in conf file makes arbiter fail in a nasty way Created: 21/Apr/16 Updated: 24/May/16 Resolved: 24/May/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.2.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Nicolai Marck Ødum [X] | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Steps To Reproduce: | 1. Create a replica set with 2 normal members and a arbiter without declaring bind_ip in conf file |
| Participants: |
| Description |
|
Begining with Mongo 3.2.5 all instances in a replica set starts with:
We have replica sets with 2 normal members and a arbiter |
| Comments |
| Comment by Kelsey Schubert [ 06/May/16 ] |
|
Hi myMarck, We still need the information I requested above to diagnose the problem. If this is still an issue for you, can you please clarify which operating system you are using and whether you are able to connect to the arbiter locally as well as from a remote host? Thank you, |
| Comment by Kelsey Schubert [ 21/Apr/16 ] |
|
Hi myMarck, We have not been able to reproduce the issue that you describe on windows, mac, or linux machines. We started a replica set without and bind_ip and inserted some data. Then we stopped the arbiter and added the bind_ip. The arbiter was still included in the configuration and behaved correctly. Restarting the other members worked fine as well.
Thank you, |