* Given a 3 node cluster: "Node A", "Node B", "Node C" * Node "A" and Node "B" are part of failover domain "FD1" * Node "B" and Node "C" are part of failover domain "FD2" * An HTTP Resource and IP Address Rresource make up a service "SV1" which is confined to failover domain "FD1" and is running exclusive. * A GFS filesystem Resource makes up a service "SV2" which is confined to failover domain "FD2" and is running as exclusive. With the above scenario in mind, assuming "SV1" is running on "Node A" and "SV2" is running on "Node B", what will occur if there is a hardware failure in "Node A"? The expected behavior would be that "SV2" would relocate to "Node C" and "SV1" would relocate to "Node B" given the failover domains, and the 'run-exclusive' restriction. Is this the case? If so, can documentation be provided to illustrate this example? In essence the desired function is to define a service as needing to run exclusive, but also being able to define the same service as more critical than another service such that if a relocate needs to occur associated with an exclusive service, the less-critical service located on another node which the critical service wishes to relocate to will either relocate to another node in the cluster, or disables itself so that the more critical exclusive service is able to start-up on the failover node.
rgmanager does not run iterative service placement in the event of failures; it lacks the dependency engine processing required. For example, in the example: * Given a 3 node cluster: "Node A", "Node B", "Node C" * Node "A" and Node "B" are part of failover domain "FD1" * Node "B" and Node "C" are part of failover domain "FD2" * SV1 is in FD1 and running on Node A * SV2 is in FD2 and running on Node B If A fails, SV1 will not recover; rgmanager does not build a list of actions to take at service failures that are related to one-another. There was code upstream at one point to give this sort of multi-action ability to rgmanager, but it was removed long ago: https://git.fedorahosted.org/cgit/cluster.git/commit/?h=STABLE32&id=52685e0f57063583d6af537d1ea2e1539e437372 Instead, the Pacemaker Cluster Resource manager will provide functionality similar to this.
Cluster Suite is no longer supported.