See Cache Cluster Discovery Overview for an introduction to the two methods of configuring a cache cluster, multicast and well-known-addresses.
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.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
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 Specifies the name of the cache cluster. Use the same name for all nodes in a cache cluster.Note Do not use the name $cluster. It is a reserved name. 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.
Copyright © TIBCO Software Inc. All Rights Reserved.