Adding and Removing Data Center Nodes
Your Data Center license is based on the number of users in your cluster, rather than the number of nodes. This means you can add and remove nodes from your Data Center cluster at any time.
If you deployed Confluence Data Center on AWS using the Quick Start, your Confluence and Synchrony nodes will be in auto-scaling groups. You will add and remove nodes in the AWS console either by changing the minimum and maximum size of each group or using a scaling plan.
On this page:
Adding a node
To add a node:
- Copy the installation directory and local home directory from the stopped node to your new node.
- Start Confluence on your new node.
During the startup process Confluence will recover indexes from a running node to bring the new node up to date. - Go to Administration menu
, then General Configuration > Clustering and check that the new node is visible.
You should only start one node at a time. Starting up multiple nodes simultaneously can cause serious failures.
If the discovery mode is set to TCP/IP, you'll need to update the confluence.cluster.peers property in the confluence.cfg.xml file for each node so the file lists all nodes in your cluster:
<property name="confluence.cluster.peers">[node 1 IP],[node 2 IP],[node 3 IP]</property> <!-- A comma-separated list of node IP addresses, without spaces -->Removing a node
To remove a node, stop Confluence on that node. You can then remove the installation and local home directory as required.
To see the number of nodes remaining go to Administration menu , then General Configuration > Clustering.
Changing the node identifier
Confluence generates an identifier for each node in your cluster. You can use the confluence.cluster.node.name system property to set the node identifier on each node so that it's easier for your users and administrators to read.
See Configuring System Properties for more information on how to set the system property.
Moving to a non-clustered installation
If you no longer need clustering, and want to avoid the overhead that comes from running a cluster with just one node, you can go back to a non-clustered Data Center installation. You'll need to make some infrastructure changes as part of the switch.
See Move to a non-clustered installation to find out how to do this.