Configure the sync server cluster by setting the following properties in the config.yml file.
Note: These properties are optional.
| Clustering property | Description |
|---|---|
| sync.cluster.enabled | Optional. This enables clustering. Example setting: true. |
| sync.cluster.interface | Optional. This specifies a particular network interface to use for clustering. It might be a wildcard value, such as 10.256.*.*, which means an attempt is made to bind with an interface having an IP address beginning with 10.256. Example setting: 10.256.*.* |
| sync.clusterCheck.timeout | Optional. This specifies the time to wait for a cluster node ping before marking the node as not alive (ms). Example setting: 4000. |
| sync.hazelcast.password | Optional. This specifies the password used by the cluster members to access or join the Hazelcast cluster. Example setting: synccluster. |
| sync.hazelcast.port | Optional. This specifies the port to use for clustering. Example setting: 5701. |
| sync.hazelcast.autoinc.port | Optional. This enables Hazelcast to make several attempts to find a free port,
starting at the value of alfresco.hazelcast.port.
CAUTION: It’s recommended that
you don’t use this property. Example setting:
false.
|
| sync.hazelcast.max.no.heartbeat.seconds | Optional. This specifies the maximum timeout of heartbeat (in seconds) for a node to assume it is dead. Example setting: 15. |
| sync.hazelcast.bind.any | Optional. This specifies if Hazelcast can bind to any/all interfaces. This must be false for the sync.cluster.interface property to have any meaningful effect. Example setting: false. |
| sync.hazelcast.mancenter.enabled | Optional. This specifies if the Hazelcast Management Center (mancenter) is being used for cluster management. See the Deploying and Starting article in the Hazelcast Management Center documentation, available at https://docs.hazelcast.com. Example setting: false |
| sync.hazelcast.mancenter.url | Optional. This specifies the mancenter URL. Example setting: http://<host-ip>:<port>/mancenter. |
Note: Ensure that clocks on all the sync server nodes (cluster members) are
synchronized using a tool like Network Time Protocol (NTP). See the NTP
Project site for more information, available at
https://www.ntp.org.
Note: Ensure that all the cluster nodes have the same settings in the
config.yml file, with one possible exception. Only change
the <sync.cluster.interface> property, if the IP address of
the cluster node is specified instead of a wildcard value.