Bitbucket Server Data Center cluster only contains one node
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
Unable to create Bitbucket Server Data Center cluster, only one node registered.
Diagnosis
If a node that is visible is stopped/shutdown, another node is registered in the cluster but restarting the previous node does not add it to the cluster.
Also, restarting Bitbucket Server Data Center does not resolve the issue
Cause
Bitbucket Server Data Center has been configured to use multicast but the network does not support it.
Resolution
Switch from multicast to TCP/IP
1. Stop cluster nodes.
2. In $BITBUCKET_HOME/shared/bitbucket.properties change hazelcast.network.multicast=true to hazelcast.network.multicast=false
3. In the same file, uncomment or add the following line:
hazelcast.network.tcpip=true
4. Also in that file, uncomment or add the following line and use the the node IPs and port for the members:
hazelcast.network.tcpip.members=10.xx.xxx.xx:xxxx,10.xx.xxx.xx:xxxx
5. Restart the nodes.
More info on the process can be found here: Installing Bitbucket Data Center (see #7. Start the first cluster node).
Was this helpful?