Second node is not showing on Confluence clustering even though its healthy from AWS instace

Gaurav Bade
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 7, 2024

We are using confluence data center version. we configure our confluence on EC2 instance. Now we are trying to go into clustering node. made neccessary changes as per documentation. From AWS 2 instance are healthy but 2nd instance is not adding to clustering when i checked it from confluence interface

1 answer

0 votes
Humashankar VJ
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 7, 2024

Hi @Gaurav Bade 

To ensure proper configuration, verify that both nodes possess identical confluence.cfg.xml files, with particular attention to clustering-related properties.

Confirm that the confluence.cluster.join.type parameter is correctly set to "tcp_ip" for EC2 environments.

Also, ensure that confluence.cluster.peers accurately lists the private IP addresses of all nodes.

Besides, review node discovery settings to guarantee the use of the TCP-IP join mechanism, rather than multicast, for EC2.

Finally, double-check that the confluence.cluster.peers property contains the correct IP addresses.

 

Hope this helps - Happy to help further!!
Thank you very much and have a great one!
Warm regards

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
8.15
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events