Specifications

Available Witness Modes
# This can be either off/none or remote_verify. In remote_verify
# mode, core event handlers (comm_down) will doublecheck the
# death of a system by seeing if other visible nodes
# also think it is dead.
QUORUM_LOSS_ACTION=fastboot
# This can be one of osu, fastkill or fastboot.
# fastboot will IMMEDIATELY reboot the system if a loss of quorum
# is detected.
# fastkill will IMMEDIATELY halt/power off the system upon
# loss of quorum.
# osu will just take any in-service resources out of service.
# Note: this action does not sync disks or unmount filesystems.
QUORUM_DEBUG=
# Set to true/on/1 to enable debug messages from the Quorum
# modules.
HIDE_GUI_SYS_LIST=1
Note: Due to the inherent flexibility and complexity of this mode, it should be used with caution by
someone experienced with both LifeKeeper and the particular network/cluster configuration involved.
none/off
In this mode, all quorum checking is disabled. This causes the quorum checks to operate as if the
node always has quorum regardless of the true state of the cluster.
Available Witness Modes
Two witness modes are available which can be set via the WITNESS_MODE setting in the
/etc/default/LifeKeeper: remote_verify and none/off. Each of these is described below:
remote_verify
In this default mode, witness checks are done to verify the status of a node. This is typically done
when a node appears to be failing. It enables a node to consult all the other visible nodes in the cluster
about their view of the status of the failing machine to double-check the communications.
none/off
In this mode, witness checking is disabled. In the case of a communication failure, this causes the
logic to behave exactly as if there was no witness functionality installed.
Note: It would be unnecessary for witness checks to ever be performed by servers acting as
dedicated quorum/witness nodes that do not host resources; therefore, this setting should be set to
none/off on these servers.
SteelEye Protection Suite for Linux109