Chapter 20 Configuring Cache Cluster Settings : Example Cluster Configuration Properties

Example Cluster Configuration Properties
The examples below show cluster configuration properties that are set to the same values in engine property files for all nodes in the cluster, and those that can be different in each node, and the Decision Manager related properties that are required only if Decision Manager is used, and that are set in one or more nodes as needed.
The examples show a set of cluster-level configuration properties enabling multicast discovery of cluster members, a distributed cache, and no backing store.
Other Lists of Engine Properties
The lists below focus on cluster-level properties. Other properties are listed in the following sections:
In the examples below, some example values are provided. Most properties have default values and can be omitted if the default value is suitable.
Cluster Properties That Must be the Same in All Nodes

 
# Cluster name:
java.property.tangosol.coherence.cluster Acme
 
# Multicast cluster member discovery:
java.property.tangosol.coherence.clusteraddress=224.3.3.1
java.property.tangosol.coherence.clusterport=33389
java.property.tangosol.coherence.ttl=4
 
# OR
# Well-known-address cluster member discovery:
# java.property.tangosol.coherence.wka1=hostname1
# java.property.tangosol.coherence.wka1.port=8088
# java.property.tangosol.coherence.wka2=hostname2
# java.property.tangosol.coherence.wka2.port=8088
 
# Cache cluster properties:
be.engine.cluster.hasBackingStore=false
be.engine.cluster.isCacheLimited=false
java.property.be.engine.limited.cache.back.size.limit
be.engine.cluster.multiEngineOn=true
java.property.tangosol.coherence.distributed.backupcount=2
be.engine.cluster.minCacheServers=2
java.property.tangosol.coherence.distributed.threads=10
 
# If Operational Descriptor Override File is used:
java.property.tangosol.coherence.override=file:/c:/tmp/my_tangosol-coherence-override.xml

 
Use of an operational descriptor override is not generally required. For details see Overriding and Extending the Operational Deployment Descriptor and Specifying Operational Override File Locations.
Cluster Properties That Can Differ Across Nodes
(The cache server property is not exactly a cluster property, but for sake of completeness it is included here.)

 
# Cache logging properties
java.property.tangosol.coherence.log.level=3
java.property.tangosol.coherence.log=sterr
java.property.tangosol.coherence.log.limit=4096
 
# Local Storage
java.property.tangosol.coherence.distributed.localstorage=true
 
# Deploy this node as a cache server?
be.engine.cacheServer=true
 
# If multiple hosts exist on one machine:
java.property.tangosol.coherence.localhost=
java.property.tangosol.coherence.localport=

 
Cluster Properties Set in Some Nodes, As Needed

 
# If Decision Manager is Used:
be.engine.cluster.externalClasses.classLoader=true
be.engine.cluster.externalClasses.path=c:/myfolder/