Product SiteDocumentation Site

Chapter 4. Cluster Nodes

Table of Contents

4.1. Defining a Cluster Node
4.2. Where Pacemaker Gets the Node Name
4.3. Node Attributes
4.4. Managing Nodes in a Corosync-Based Cluster
4.4.1. Adding a New Corosync Node
4.4.2. Removing a Corosync Node
4.4.3. Replacing a Corosync Node
4.5. Managing Nodes in a Heartbeat-based Cluster
4.5.1. Adding a New Heartbeat Node
4.5.2. Removing a Heartbeat Node
4.5.3. Replacing a Heartbeat Node

4.1. Defining a Cluster Node

Each node in the cluster will have an entry in the nodes section containing its UUID, uname, and type.

Example 4.1. Example Heartbeat cluster node entry

<node id="1186dc9a-324d-425a-966e-d757e693dc86" uname="pcmk-1" type="normal"/>

Example 4.2. Example Corosync cluster node entry

<node id="101" uname="pcmk-1" type="normal"/>

In normal circumstances, the admin should let the cluster populate this information automatically from the communications and membership data. However for Heartbeat, one can use the crm_uuid tool to read an existing UUID or define a value before the cluster starts.