When you start a Nexus Repository 3 cluster configured for TCP/IP, each node selects a network interface to use. Depending on which one is selected, the nodes of the cluster may not be able to communicate. This problem can be avoided by specifying the network interface for each node in the hazelcast-network.xml.
When you configure Hazelcast as a TCP/IP cluster, you include a list of the member IP addresses.
When each cluster member starts it will attempt to connect to the other nodes using the addresses specified in the member-list.
Servers may have more than one network interface. When the node starts up, it will pick one address from the available TCP-IP addresses to use as its cluster network interface. If it chooses one that cannot be used for communication between cluster nodes, then it will not be able to join the cluster. To avoid this problem, you can specify the network interface for each cluster node.
Each node will use its own interface address, as shown below.
These values are configured in the hazelcast-network.xml file located here: