HaCluster Client on backends

The HaCluster Client helps the HaCluster balancer service to correctly judge nodes health.

The HaCluster Client service is available with Artica version 4.30 and unstable Service Pack 879 or higher or with Artica version 4.40

The purpose of the HaCluster Client is to listen on the TCP 27899 port and wait periodic connections from the main HaCluster load-balancing service.
The period can be tuned in the Heath Check section
When the main HaCluster service query the HaCluster Client port, it checks the health of the local server and the proxy service.
If the Proxy service is OK an HTTP return code 200 is sent. Otherwise, and HTTP error code 500 is sent.

Deploy the HaCluster Client.

The HaCluster Client is activated centrally through the HaCluster Load-balancer. In this case, all managed nodes must have the minimum recommended version.

On the left menu, choose “HaCluster / Backends”
Select “Central Configuration” tab.
Turn ON the “Use HaCluster Client” option.
Click on Apply button

After reconfigure nodes, if there is a connection issue on the 27899 port a specific disconnect icon is displayed

You can click on it to see the error description.

Automatic status report

If the HaCluster Client report a false status, the HaCluster Load-balancer automatically stop the node and connections will redirected to the available proxy in the farm.

You can see logs reports on the HaCluster Client on nodes using the “HaCluster / Backends events” section
On the search field,type “HaClusterClient”