[SERVER-70786] Is there any solution adding multiple IP to replicaSet member for host name on MongoDB? Created: 24/Oct/22 Updated: 25/Oct/22 Resolved: 25/Oct/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | 팍 제이티 | Assignee: | Chris Kelly |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
I am really in trouble with the replSet option using multiple IPs on another network (A net and B net). I have 3 PCs and they have 2 LAN ports for each computer and they are separated by A net and B net. I can use replSet option and make a binding IP (--bind_ip 127.0.0.1,192.168.0.233,192.168.0.234) But I can not make the member in rs.config for all IPs. It just allows one IP for each PC. So, I can not connect to MongoDB using the B network if the A network which is set in the member is dead. Is there another solution to my situation? |
| Comments |
| Comment by Chris Kelly [ 25/Oct/22 ] |
|
Hello, Thanks for your report. This is currently unsupported behavior as per SERVER-36603, but it's on the backlog. In the meantime, I would look to see if you can consider using a DNS or other intermediary service to get around defining multiple IP's in the replica set at this time. In this case, you may find additional information by asking our community for help by posting on the MongoDB Developer Community Forums as well as checking out the linked ticket for updates. If the discussion there leads you to suspect a bug in the MongoDB server, then we'd want to investigate it as a possible bug here in the SERVER project. Regards, Christopher |