Define the Master Cluster.
The Master Cluster is one Artica server that holds the configuration set. It's on this server that you need to administer the proxy settings so that the farm replicates the settings on the clones.
The Master Cluster is one Artica server that holds the configuration set.
It's on this server that you need to administer the proxy settings so that the farm replicates the settings on the clones.
It uses the HaCluster load-balancer as a reference to the Cluster package.
When you modify the configuration on the Master server, it will generate a Cluster package.
The master server will push the Cluster package onto the load-balancer.
As soon as the load-balancer receives the cluster package, it will deploy it on the nodes hosted by the cluster farm.

Set the Master server
- On the left menu Go to
HaCluster > Backends - Click on the Backend you want as Cluster master.
- On the backend settings, turn on the “Master Proxy” option.
- This master server is part of the node cluster and handles user requests like a node in the farm.
Since this server becomes sensitive as it hosts the farm's configuration, you can disconnect it from user traffic by enabling the "disconnect from farm" option.
This way, it will remain part of the farm but will no longer be used for web traffic.

Test the replication
- Go to the Artica Web interface of this master server.

- On the left menu, go to “
Your System > Cluster ( Master mode )" - Click on “Build Cluster package” button in order to build a new cluster package for replication

- A new package is generated and have few seconds of live.

Verify the replication on the Load-balancer service
- Go on the HaCluster load-balancer web interface
- On the left menu, select
HaCluster > Status - Take a look on the text under the title, you will see the address of the Master server and the uploaded duration of the package.
