Clustering FAQ

Here are some frequently asked questions and answers about clustering.

Do all cluster members need to be on the same local network?

Yes. It's better for performance.

Is it possible to have more than one cluster per physical network?

You can have two deployments (for example, CommunityA and CommunityB) on the same physical network operating as two clusters. You cannot have a single deployment (for example, CommunityA) separated into two clusters.

How do configuration files work in a cluster?

All configuration data (except bootstrap information such as database connection information) is stored in the database. Changing configuration settings on one cluster member will automatically update them on all other cluster members.

Can I set a cluster node's TCP endpoint to a particular value?

Yes. If you have an address and port you want to force a node to bind to, you can do that by setting those values in the Admin Console. If you do that, the node tries that address and port only; it won't scan for an address and port if the one you specify fails. For more information, see Configuring cluster node (optional).

How will I know if a cluster node has failed or can't be found by the cluster?

The Cluster page in the Admin Console displays a list of nodes in the cluster. See Configuring cluster node (optional) for more information.