Cluster Discovery and Internal Communication
When you add a CDD file and select Cache OM type, you must configure how the members of the cache cluster discover each other at runtime and communicate with each other once the cluster is established.
This section has summary steps for both cache providers, and pointers to sections with more details.
Support for Host-Aware Replication
Host-aware replication for ActiveSpaces is controlled by the property be.engine.cluster.as.hostaware.enable. Host-aware replication requires that the member name be a 2-part name separated by a "."
By default, this property is true ( or enabled ).
- If
true, the ActiveSpaces member name will be set as:
hostname.be-engine-name
where be-engine-name is what is given on the -n command line option. When host-aware replication is enabled, if the cache nodes are not deployed on multiple machines to satisfy replication by the host, then replication will not happen (or will happen only according to the number of hosts available).
For example, if "Number of Backup Copies" is set to "1" and all cache nodes are deployed on a single host, then replication will be disabled (regardless of the number of cache nodes on that single host). If "Number of Backup Copies" is set to "2", and cache nodes are deployed only on 2 hosts, then only "1" backup copies will be maintained.
- If the property is false, host-aware replication will be disabled and the ActiveSpaces member name will be set as be-engine-name. Disabling hostaware replication will honor "Number of Backup Copies", provided that there are enough cache nodes deployed in the cluster.