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:
Database\repository\spectrum-container.properties
This table describes each property:
| Property | Description |
|---|---|
| spectrum.cluster.enabled | Indicates whether a clustered configuration is used. Set this to true. |
| spectrum.cluster.name | 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.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, specify the host name
or IP address of each of the other nodes in the cluster, including nodes that you
have not yet installed. Separate each seed node with a comma. When starting up, this
property should be set to all nodes in the cluster when cluster.enabled =
true. 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. |