Novell SUSE LINUX ENTERPRISE SERVER 10 SP2 HEARTBEAT Manual page 20

Designated Coordinator. You can use either tool on any node in the cluster, and the
local CIB will relay the requested changes to the Designated Coordinator. The Desig-
nated Coordinator will then replicate the CIB change to all cluster nodes and will start
the transition procedure.
With help of the Policy Engine and the Transition Engine, the Designated Coordinator
obtains a series of steps that need to be performed in the cluster, possibly on several
nodes. The Designated Coordinator sends commands out via the messaging/infrastructure
layer which are received by the other Cluster Resource Managers.
If necessary, the other Cluster Resource Managers use their Local Resource Manager
to perform resource modifications and report back to the Designated Coordinator about
the result. Once the Transition Engine on the Designated Coordinator concludes that
all necessary operations are successfully performed in the cluster, the cluster will go
back to the idle state and wait for further events.
If any operation was not carried out as planned, the Policy Engine is invoked again
with the new information recorded in the CIB.
When a service or a node dies, the same thing happens. The Designated Coordinator
is informed by the Cluster Consensus Membership service (in case of a node death) or
by a Local Resource Manager (in case of a failed monitor operation). The Designated
Coordinator determines that actions need to be taken in order to come to a new cluster
state. The new cluster state will be represented by a new CIB.
12 Heartbeat