Need to Cluster our Confluence Setup which is serving on Single Server

unknown

Hello,

We configured confluence on single server to support one of our application in AWS. In order support our site to provide high availability, scalable capacity, and performance at scale we are planning to cluster our environment by having multiple nodes. So, can you please support us by providing the support and what are all the steps required to follow to migrate to cluster environment. I did follow the below documentation for the setup and I have multiple questions regarding the  Step 6. Configure your cluster.

https://confluence.atlassian.com/doc/set-up-a-confluence-data-center-cluster-982322030.html

Question 1) Which is the best process to follow to provide the IP's or AWS - enter your IAM Role or secret key, and region?

Question 2) if we provide the IP's and if suppose we lost one node and wanted to configure another node and replace the IP. Is there any process or steps we need to follow?

Question 3) can you explain more on the The network interface Confluence will use to communicate between nodes. We know about Elastic Network Interface but not sure what exactly needs to provide here?

 

We currently want to implement this in our Stage Environment and move to prod later after successful migration.

 

Thanks,

Ramesh

Laurens Coppens

Hi Ramesh,

 

1) is stated in the documentation: 

We recommend using our Quick Start or Cloud Formation Template to deploy Confluence Data Center in AWS, as it will automatically provision, configure and connect everything you need.

If you do decide to do your own custom deployment, you can provide the following information to allow Confluence to auto-discover cluster nodes:

Field	Description
IAM Role or Secret Key	This is your authentication method. You can choose to authenticate by IAM Role or Secret Key.
Region	This is the region your cluster nodes (EC2 instances) will be running in.
Host header	Optional. This is the AWS endpoint for Confluence to use (the address where the EC2 API can be found, for example 'ec2.amazonaws.com'). Leave blank to use the default endpoint.
Security group name	Optional. Use to narrow the members of your cluster to only resources in a particular security group (specified in the EC2 console).
Tag keyand Tag value	Optional. Use to narrow the members of your cluster to only resources with particular tags (specified in the EC2 console).

 

2) you can add additional nodes to your node configuration.

Add more Confluence nodes

Your Data Center license doesn’t restrict the number of nodes in your cluster. To achieve the benefits of clustering, such as high availability, you’ll need to add at least one additional cluster node.

We’ve found that typically between 2 and 4 nodes is sufficient for most organizations. In general we recommend starting small and growing as needed.

7. Copy Confluence to the second node

 

To copy Confluence to the second node:

 

1. Shut down Confluence on node 1.
2. Copy the installation directory from node 1 to node 2.
3. Copy the local home directory from node 1 to node 2.

Copying the local home directory ensures the Confluence search index, the database and cluster configuration, and any other settings are copied to node 2.

 

 

Copying the local home directory ensures the Confluence search index, the database and cluster configuration, and any other settings are copied to node 2.

Make sure your database has sufficient connections available to support the number of nodes.

 

 

3) as far as i know, confluence uses the default network adaptor to connect both inter node traffic and load balancer traffic.

 

Hope this helps,

Laurens