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.
Start Confluence on one node without the
synchrony.service.urlsystem property. This property tells Confluence where to find your external Synchrony cluster.Show me how to do this...
The way you remove this system property depends on how you run Confluence. Note that this system property is passed to Confluence, not Synchrony itself.
If you start Confluence manually on Windows, edit the
<install directory>/bin/setenv.batfile and remove the following line:
set CATALINA_OPTS=-Dsynchrony.service.url=http://example-synchrony.com/synchrony/v1 %CATALINA_OPTS%
If you start Confluence manually on Linux, edit the
<install directory>/bin/setenv.shfile and remove the following line:
If you're running as a Confluence as a Windows Service, you'll need to edit the service and remove the following from the Java options:
See Configuring System Properties for a step-by-step guide to passing system properties to Windows services via the command line or Windows Registry.
- 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.