Add properties as needed to configure multicast cluster member discovery, or well-known address cluster member configuration. Also define the backup count for cluster objects.
If you used the Wizard to set the object manager, a property group called coherence contains all the multicast discovery properties and the backup count property.Groups are for convenience only. You can group properties differently or not at all, as you find convenient.If you are using well-known addresses for cluster member configuration, delete the multicast properties and instead add the well-known address properties.
The backup count specifies the number of members of the distributed cache service that hold the backup data for each unit of storage in the cache. Recommended values are 0, 1, or 2.Value of 0 means that in the case of abnormal termination, some portion of the data in the cache will be lost. Value of N means that if up to N cluster nodes terminate at once, the cache data will be preserved.A backup count of 1 means one server plus one backup, that is, two cache servers (or storage enabled nodes if cache servers are not used).To maintain the partitioned cache of size M, the total memory usage in the cluster does not depend on the number of cluster nodes and will be in the order of M*(N+1). If you will define cluster members using multicast discovery properties, use the properties in this section, instead of those in the section Well-Known Address Properties. Use this setting if multicast discovery is used and if you need a non-default value. Specifies the multicast IP address that the socket will listen to or publish on.Possible values are addresses between (and including) 224.0.0.0 and 239.255.255.255.Default value is 224.3.3.1 Use this setting if multicast discovery is used and if you need a non-default value. Specifies the port that the socket will listen to or publish on. Specifies the time-to-live setting for the multicast, that is, the maximum number of "hops" a packet can traverse. A hop is defined as a traversal from one network segment to another via a router.For production use, set this value to the lowest integer value that works. Setting the value too high can use unnecessary bandwidth on other LAN segments and can even cause the operating system or network devices to disable multicast traffic.On a single-host cluster, set to zero (0). On a simple switched backbone, set to 1. On an advanced backbone with intelligent switching, it may require a value of 2 or more.Note: A value of 0 is intended to keep packets from leaving the originating machine. However, some operating systems do not implement this correctly, and the packets may in fact be transmitted on the network. These properties are used by multicast discovery and well-known address configuration when a host has multiple network cards.You can put default values here. However if you need to use these properties in the case of multiple network cards, add them as Processing Units tab properties. Localhost [or was it localport?] can also be used when more than one cluster is running on the same subnet and multicast is used. Even even though they have different cluster names, if they use the same cluster address, you may need to specify this property to avoid conflict.Note Also used for well-known address configuration, for the same situation.You can generally set the value of the localhost property to the value "localhost." However, if localhost is used as the loop back address (127.0.0.1) you must enter a machine name or IP address.Default value is localhost. Specifies the port that the socket will listen to or publish on.If more than one cluster is running on the same subnet, then even though they have different cluster names and cluster addresses, you may need to specify this property to avoid conflict.Note If a specified port is not available, the object management layer (by default) increments the port number until it finds an available port. Avoid potential conflicts by choosing a number that is not close to a port used by other software in your environment.You can turn off the auto-incrementing feature. To turn off auto-incrementing, add the following property in the Cluster Tab> Properties section and set the value of the following override option to false: If you will define cluster members using well-known addresses, use the properties in this section, instead of those in the section Multicast Discovery Properties.Note 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. 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. Enter all the well known addresses and ports for machines used by the cluster. For port, enter a value between 1 and 65535.Note If multiple processing units (PUs) run on the same host machine, configure with two addresses for the same machine, and use a different port number for each. For example:Tip An auto-incrementing feature ensures that a different port is used if one specified is already in use. If you have customized the cache configuration file, specify the file path and name of the customized file. The default file is located in the BE_HOME/lib/ext/coherence.jar file and is called:
Copyright © TIBCO Software Inc. All Rights Reserved.