Migrate from a standalone Synchrony cluster to managed Synchrony
If you have a Confluence Data Center license, and enabled collaborative editing prior to Confluence 6.12, you will likely be running standalone Synchrony, either in it's own cluster, or manually on each Confluence node.
If you'd prefer a simpler setup, with less ongoing maintenance, you can choose to let Confluence manage Synchrony for you. Confluence will automatically start up a Synchrony process when Confluence is started.
Some Confluence downtime is required for this process.
To switch from managing your own Synchrony cluster to letting Confluence manage Synchrony:
- Configure your load balancer to direct traffic away from all Confluence and Synchrony nodes.
- Stop Confluence and Synchrony on all nodes.
Remove the the
synchrony.service.urlsystem property. This property tells Confluence where to find your external Synchrony cluster.Set the
synchrony.memory.maxsystem property to increase the maximum heap memory available to Synchrony to 2gb (or the amount of memory previously allocated to the Synchrony standalone service).- Start Confluence on one node.
- In Confluence, edit a page and check that you can successfully make changes.
- Repeat this process on each Confluence node, starting each node one at a time.
Once all nodes are back up and running, and you've confirmed that collaborative editing is working as expected, you can decommission your external Synchrony cluster, including removing any startup scripts or services you may have configured.
Any users who had the editor open before you made this change will need to refresh in order to continue editing, as the Synchrony URL they're connected to will have changed.
You may also need to make some changes to your load balancer configuration. See Possible Confluence and Synchrony Configurations for more information.