Details
-
New Feature
-
Status: Closed
-
Major - P3
-
Resolution: Won't Do
-
1.7.0
-
None
-
None
-
Service Arch
-
(copied to CRM)
Description
Problem:
In order to scale network traffic for client connections and replication traffic, there are two options
a) add a NIC
b) swap out a 1Gig for a 10Gig Ethernet Card
Case b) is already supported. However, to support case a) we would need to be able to specify different networks for
– client connections (and failover of client connections)
– replication connections
Impact:
This would impact
– mongod would need to accept connections over more than a single interface
– replSetInitate configuration would need the ability to specify a different ip/port for the replication traffic
Other:
Would need test cases for the client nic failover from the replication nic failover.
Attachments
Issue Links
- is duplicated by
-
SERVER-40314 Cannot connect to replica set
-
- Closed
-
-
SERVER-26817 replset member connect to each other through a proxy
-
- Closed
-
-
SERVER-34060 Intranet & Internet Address in mongodb replica set
-
- Closed
-
-
SERVER-3098 Allow replica sets to use separate network interface for replication.
-
- Closed
-
-
SERVER-22321 Can I use several IP addresses for Replication and Backup?
-
- Closed
-
- is related to
-
DOCS-8596 Make clear in server docs as well as driver docs that the rs.config must contain only host names that can be resolved by drivers.
-
- Closed
-
-
SERVER-20461 Write tests to verify replica set operation in case of traffic segregation by hostname
-
- Backlog
-
-
SERVER-36603 Support for multiple hostnames and IPs in MongoDB replica sets for high availability
-
- Backlog
-
- related to
-
SERVER-34986 CIDR Block That is Exempt from maxConns
-
- Closed
-
- links to