Anybody who has implemented Confluence Data Center 6.0 through 6.11 likely knows that Atlassian has made huge strides in how Synchrony is deployed. But none of those strides have been as awesome as the change introduced in v6.12. From v6.12 forward Confluence Data Center nodes can each manage their own synchrony services! No more modifying your start-synchrony.sh file with all the necessary details (but if you aren’t on this version yet, check out my blog on how to automatically populate it via a shell script). Check out the reference architecture: check out my blog

Some of you may be asking how you switch from an existing deployment running an unmanaged Synchrony process to this new hotness. It’s easier than you may think!

First, you’ll want to stop both the Synchrony and Confluence service.

Second, remove the synchrony.service.url option in your setenv.sh file.

That’s it! Now you can start your Confluence server and it will spin up a Synchrony process for you.

There are some other things to be away of with using this deployment option of Synchrony. see the above linked architecture link for some of those gotchas.