Details
Description
What?
Allow configuring traffic flow for client app and intra cluster traffic over specific IPs on nodes with multiple IPs.
Why?
- Cloud: Most public clouds and multi DC enterprise deployments use nodes with 2 IPs - public and private - private IPs are configured to be a specific local subnet (10.0.0.x type addresses) in public cloud these addresses provide lower and predictable latencies as opposed to the public IPs which require a roundtrip to the outer edge of the DC hitting more switches and routers along the way. private IPs also give you better fault isolation with less equipment/hops between 2 nodes.
- Segregate Traffic and network load: If customers are concerned about network saturation during events like rebalance, this type of separation at the network card level can help isolate impact of rebalance traffic on client app traffic etc. this is also good for things admin tasks, large data import/export operations or other network heavy admin tasks etc.
In this type of setups, typically most customers would like public IP for XDCR or remote client apps and want private ips for local client apps + intra cluster (replication, rebalance etc) communication.
Workaround:
Today you can workaround this by defining dns mapping in the hosts file, however it makes it convoluted to add nodes as you first need to deploy the hosts files to the existing and new nodes and then do the cluster level operations.
Attachments
Issue Links
- duplicates
-
MB-4112 Support different network interfaces for client vs intra cluster communication
- Closed