Cluster Properties for a Configuration Database Cluster

A configuration database cluster is a cluster where each node contains the configuration database only, and not the server. If you are setting up a cluster where the server and configuration database are installed together on each node, or are setting up a server-only cluster, see Cluster Properties.

The settings for a configuration database cluster are located in this properties file:


This table describes each property:

Property Description
spectrum.cluster.enabled Set this to true. If this is the first node in the cluster, set this to any name you want to give to the configuration database cluster. Be sure that the name is unique if you have multiple clusters.

If you are adding a node to an existing cluster, set this to the name of the configuration database cluster that you want this node to join.

spectrum.cluster.address Specify the node's own IP address.
spectrum.cluster.seeds If you are setting up the first node in the cluster, or if this is the first node you are starting after having stopped the cluster, specify only the host name or IP address of this server. This effectively points this node to itself as a seed node, which is necessary in order for it to be able to start as the first node in the cluster.
If this is not the first node in the cluster, use the host name or IP address of the Spectrumâ„¢ Technology Platform server whose configuration will be replicated on this node when it joins the cluster, resulting in synchronized configuration. You can specify multiple seed nodes by separating each with a comma. When starting up, the node will attempt to access each seed node in the order listed. If none of the seed nodes can be reached, the node will not join the cluster.
Tip: We recommend that you specify multiple seed nodes so that if one seed node is down others can be used to allow nodes to join the cluster. We also recommend that you specify the same seed nodes in the same order on all nodes in the cluster.
spectrum.cluster.nodeID Set this to an integer value to use as the ID for this node. The ID must be an integer and must be unique among all nodes in the database cluster. For example, you could set the node ID for the first node to 1, the second node's node ID to 2, and the third node's node ID to 3.