Chapter 4. Configuring and Managing Cluster Resources / 4.10. Configuring a Heartbeat Clone Resource | ||||
|---|---|---|---|---|
 | 4.9. Configuring a Heartbeat Cluster Resource Group | 4.11. Migrating a Cluster Resource |  | |
Chapter 4. Configuring and Managing Cluster Resources / 4.10. Configuring a Heartbeat Clone Resource | ||||
|---|---|---|---|---|
| 4.9. Configuring a Heartbeat Cluster Resource Group | 4.11. Migrating a Cluster Resource | | |
You may want certain resources to run simultaneously on multiple nodes in your cluster. To do this you must configure a resource as a clone. Examples of resources that might be configured as clones include STONITH and cluster file systems like OCFS2. You can clone any resource provided it is supported by the resource’s ResourceAgent. Clone resources may even be configured differently depending on which nodes they are hosted.
There are three types of resource clones:
Anonymous Clones: These are the simplest type of clones. They behave identically anywhere they are running.
Globally Unique Clones: These resources are distinct entities. An instance of the clone running on one node is not equivalent to another instance on another node; nor would any two instances on the same node be equivalent.
Stateful Clones: Active instances of these resources are divided into two states, active and passive. These are also sometimes referred to as primary and secondary, or master and slave. Stateful clones can be either anonymous or globally unique.
To configure a resource as a clone, follow Step 1 through Step 6 in Section 4.2, “Creating Cluster Resources”.
Select the check box. This will allow the resource to simultaneously run on multiple cluster nodes.
In the field, enter the number of instances of the resource that will run on a given node.
In the field, enter the number of nodes in the cluster that will run the resource.
Click to add the clone resource to the cluster.
Select the resource in the left pane and click + to start the resource. Starting the clone resource will cause it to start on the nodes that have been specified with its resource location constraints.
After creating the resource, you must create location constraints for the resource. The location constraints determine which nodes the resource can run on. See Constraints on the High Availability Linux Web site.
