• Configured with one GULM server — Quorum equals one GULM server.
• Configured with three GULM servers — Quorum equals two GULM servers.
• Configured with five GULM servers — Quorum equals three GULM servers.
The cluster manager keeps track of membership by monitoring heartbeat messages from other
cluster nodes. When cluster membership changes, the cluster manager notifies the other
infrastructure components, which then take appropriate action. For example, if node A joins a
cluster and mounts a GFS file system that nodes B and C have already mounted, then an
additional journal and lock management is required for node A to use that GFS file system. If a
cluster node does not transmit a heartbeat message within a prescribed amount of time, the
cluster manager removes the node from the cluster and communicates to other cluster
infrastructure components that the node is not a member. Again, other cluster infrastructure
components determine what actions to take upon notification that node is no longer a cluster
member. For example, Fencing would fence the node that is no longer a member.
Figure 1.2. CMAN/DLM Overview
Chapter 1. Red Hat Cluster Suite Overview
6
Summary of Contents for CLUSTER SUITE FOR ENTERPRISE LINUX 4.5
Page 4: ...Red Hat Cluster Suite Overview ...
Page 6: ...vi ...
Page 19: ...Figure 1 4 Power Fencing Example Fencing 9 ...
Page 21: ...Channel Connections Figure 1 6 Fencing a Node with Dual Power Supplies Fencing 11 ...
Page 34: ...Figure 1 17 Conga LVM Graphical User Interface Chapter 1 Red Hat Cluster Suite Overview 24 ...
Page 49: ...Figure 1 25 luci homebase Tab Figure 1 26 luci cluster Tab Conga 39 ...
Page 76: ...66 ...
Page 78: ...68 ...