Specifications

Available Quorum Modes
Available Quorum Modes
Three quorum checking modes are available which can be set via the QUORUM_MODE setting in
/etc/default/LifeKeeper: majority (the default), tcp_remote and none/off. Each of these is
described below:
majority
The majority setting, which is the default, will determine quorum based on the number of visible/alive
LifeKeeper nodes at the time of the check. This check is a simple majority -- if more than half the total
nodes are visible, then the node has quorum.
tcp_remote
The tcp_remote quorum mode is similar to majority mode except:
l servers consulted are configured separately from the cluster and its comm paths (these
servers do NOT have to have LifeKeeper installed).
l servers are consulted by simply connecting to the TCP/IP service listening on the configured
port.
Additional configuration is required for this mode since the TCP timeout allowance (QUORUM_
TIMEOUT_SECS) and the hosts to consult (QUORUM_HOSTS) must be added to
/etc/default/LifeKeeper. An example configuration for tcp_remote is shown below:
QUORUM_MODE=tcp_remote
# What style of quorum verification do we do in comm_up/down
# and lcm_avail (maybe other) event handlers.
# The possible values are:
# - none/off: Do nothing, skip the check, assume all is well.
# - majority: Verify that this node and the nodes it can reach
# have more than half the cluster nodes.
# - tcp_remote: Verify that this node can reach more than half
# of the QUORUM_HOSTS via tcp/ip.
QUORUM_HOSTS=myhost:80,router1:443,router2:22
# If QUORUM_MODE eq tcp_remote, this should be a comma delimited
# list of host:port values – like
myhost:80,router1:443,router2:22.
# This doesn't matter if the QUORUM_MODE is something else.
QUORUM_TIMEOUT_SECS=20
# The time allowed for tcp/ip witness connections to complete.
# Connections that don't complete within this time are treated
# as failed/unavailable.
# This only applies when the QUORUM_MODE is tcp_remote.
WITNESS_MODE=remote_verify
108Configuration