Summary (Customer's use case)

When a node in a Data Center experiences some errors such as disconnecting to the database, Hazlecast should be able to automatically remove it from the cluster, thus stopping the load balancer from forwarding traffic to the node.

Current outcome

A node remains in the cluster when it looses connection to the database. This results in the load balancer forwarding traffic to the node which results in errors for clients accessing resources from that node

Expected result

Whenever a node within a Data Center cluster encounters errors such as not connecting to the database, it should be disconnected from the cluster.