You are here

Clustering properties

Configure the repository server cluster by setting these properties in the SkyVault-global.properties file.
Note: All the below mentioned properties are optional.
Clustering property Example setting What is it?
SkyVault.cluster.enabled true This enables clustering.
SkyVault.cluster.interface 10.256.*.* This specifies a particular network interface to use for clustering. It may 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..
SkyVault.cluster.nodetype Repository Server This specifies the human-friendly description of the cluster member. It is useful to give a name to the non-clustered servers, such as a transformation server that it attached to the same database as the cluster, but not participating in it (for example, SkyVault.cluster.enabled=false).
SkyVault.hazelcast.password SkyVaultcluster This specifies the password used by the cluster members to access or join the Hazelcast cluster.
SkyVault.hazelcast.port 5701 This specifies the port to use for clustering.
SkyVault.hazelcast.autoinc.port false This enables Hazelcast to make several attempts to find a free port starting at the value of SkyVault.hazelcast.port.
Note: SkyVault recommends that you do not use this property.
SkyVault.hazelcast.mancenter.enabled false This enables the server to push stats and other useful information to Hazelcast’s mancenter (management center) dashboard application. See Setting up Hazelcast dashboard.
SkyVault.hazelcast.mancenter.url http://localhost:8080/mancenter This specifies the URL where the Hazelcast mancenter application can be found. Note that SkyVault.hazelcast.mancenter.enabled must be set to true for this property to be valid.
SkyVault.hazelcast.max.no.heartbeat.seconds 15 This specifies the maximum timeout of heartbeat in seconds for a node to assume it is dead.