Chapter 19 Configuring Cache Cluster Discovery : Discovering Cache Cluster Members Using Well-Known-Addresses

Discovering Cache Cluster Members Using Well-Known-Addresses
See Cache Cluster Discovery Overview for an introduction to the two methods of configuring a cache cluster, multicast and well-known-addresses.
Adding, Removing, and Moving Nodes
You must ensure that the well known address information is updated on all machines to account for system changes, such as adding, removing, and moving nodes to different machines.
If a machine changes name or IP address, the cluster continues to work correctly until the next time you restart that machine.
To Configure Well-Known-Address Settings
Enter the same set of cache cluster properties with the same values in the engine property files for all nodes in the cluster. The properties are shown below, and are described in Table 25, Cache Cluster Network Settings for Well-Known Address Protocol.

 
java.property.tangosol.coherence.cluster cluster_name
 
java.property.tangosol.coherence.wka1 host1
java.property.tangosol.coherence.wka1.port 8089
java.property.tangosol.coherence.wka2 host2
java.property.tangosol.coherence.wka2.port 8089

 
If two nodes are deployed on the same host, assign them different ports.
Provision is made for up to six well known addresses in the provided operational descriptor, using numbers 1–6. If you need more than six, see Overriding and Extending the Operational Deployment Descriptor for information about adding more well-known addresses.
 
java.property.tangosol.coherence.cluster
Note  Do not use the name $cluster. It is a reserved name.
java.property.tangosol.coherence.wkan
java.property.tangosol.coherence.wkan.port
Each "well-known-address," specifies the IP address (the value of the wkan property) and port that the socket will listen to or publish on.
For port, enter a value between 1 and 65535. If multiple instances run on the same machine, use a different port number for each.