How to Revert from Clustering to Single 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
Summary
This article does not apply to Confluence Data Center, it only applies to Confluence clustered 5.4 or earlier. For Data Center please check Move to a non-clustered installation.
Solution
Disabling a Cluster
If reverting from a Clustered configuration, one solution is to back up the data, install a new stand-alone, and restore the data. This is the recommended approach. An alternative is:
Download the standard (non-clustered) distribution from the Confluence Downloads
Point confluence-init.properties to the existing confluence-home directory.
Set in confluence.cfg.xml:
1
<property name="confluence.cluster">false</property>
To check to see if clustering has been disabled, look in the logs after the XML during startup. In your catalina.out, you have:
1
INFO [KB:main] [KB:confluence.cluster.tangosol.TangosolClusterManager] startCluster Bringing up cluster service
This line won't exist if you start it up with the config we gave above. That's how to test it.
Was this helpful?