5.13. Replicator Fencing

Continuent Tungsten can be configured to handle failures during replication
automatically and to fence the failure so that the issues do not lead to
issues with the rest of the cluster, which may lead to problems with
applications operating against the cluster. By default, the cluster is
designed to take no specific action aside from indicating and registering
the replicator so that the node will be identified as being within the
DIMINISHED or
CRITICAL state.

This behavior can be changed so that the failed replicator failure is
fenced, with configuration operating on either the master, or slave
replicators. When fencing has been enabled, the node will be placed into
either the OFFLINE state if the node
is a slave or a failover will occur if the node is a master.