[SERVER-36603] Support for multiple hostnames and IPs in MongoDB replica sets for high availability Created: 13/Aug/18  Updated: 08/Jan/24

Status: Backlog
Project: Core Server
Component/s: Replication
Affects Version/s: 3.4.0, 3.6.0, 4.0.0
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Bret Curtis Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 7
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-70786 Is there any solution adding multiple... Closed
Related
related to SERVER-1889 Support different networks / nics for... Closed
related to NODE-1711 使用K8S透過Stateful創建MongoDB的連線問題 Closed
is related to SERVER-70786 Is there any solution adding multiple... Closed
Assigned Teams:
Replication
Participants:
Case:

 Description   

Currently MongoDB can listen/bind on multiple IPs, but replicasets can only be connected to by either one hostname, fqdn or ip which makes replicasets not highly available without the use of 3rd party software.

There are solutions, such as using round-robin DNS, but they require logic on the application side to handle when the mongodb client cannot connect to an IP that was already resolved to a non-working network IP address, upwards to 50% of the time in a dual-network setup where one network is unavailable. Other solutions have their own issues as well.

Having a replicaset able to accept connections from multiple network IP addresses would resolve the need for 3rd party software and alleviate the need for an application to be re-written.



 Comments   
Comment by Hegyi Gergely [ 03/Jul/23 ]

Is there any update on this issue?

Comment by Billy Bui [ 02/Jun/20 ]

Do we have any update on this issue? My case currently is we are having production replica set using 1 interface. And for security, the servers have another interface for internal use. Then we have a backup machine plugged in internal interface (and it cannot see main interface that the replica set are configured). If we can some how make the backup machine connect to the replica set by using internal interface, that would be painless. I am currently have to work it out with IT dept to have the backup machine plugged in main interface (and it's troublesome).

Comment by Nick Brewer [ 13/Aug/18 ]

bret.curtis@wdc.com Thanks for your report. I'm passing this along to our Replication team.

-Nick

Generated at Thu Feb 08 04:43:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.