Multiple CMS server instances


I was reading through the documentation regarding deploying multiple CMS instances (pointing at the same DB) to deal with larger volumes of people. Besides expecting to have to use sticky sessions on the load balancer, I wonder if there is any additional configuration that needs to happen for the multiple instances to live side by side and update properly when the other instance writes changes to the JCR.

Do I need to configure the cluster id?

Just asking before taking the plunge to try and make it happen.




Hi Marnix,

Make sure all the CMS instances have unique cluster node ids. If you are using docker, the cluster node id is automatically assigned to hostname -f, so you don’t have to take action (in that regard, at least :slight_smile: )

Great, thanks for that!