Sometimes, when performing a synchronization operation, the node may report a failure status to the load balancer, causing it to be disconnected from the cluster. As a result, the node becomes blocked and unusable.
This feature is available on Artica v4.50 Service Pack 5 or Artica v4.50 Service Pack 4 Hotfix 20250703-19
Even if the configuration operation via synchronization fails, if you are using a master node, it is possible that the node has self-recovered using cluster replication.
As a result, you may end up with a node that is fully ready to receive connections but is not added back into the load balancer's pool.
Nodes in this state are marked with a yellow triangle.
This yellow triangle indicates that the remote node has reported a configuration or installation error and is now blocked and disconnected.
¶ Force the node back to production state
If you believe the remote node is functioning correctly and can be safely reconnected to the farm, you have two options:
- Re-synchronize the node:
Click on the icon in the “notify” column to send a re-synchronization command. - Switch to production state:
Click on the first label displaying the current primary state to manually mark the node as production-ready. - On the node status you will see the Application status in red color.
- Click on it and confirm the message to set the node in production state
