On Dec 14, 2007, at 5:46 AM, Damon Estep wrote:
I have created an order constraint that requires a DRBD/iSCSI target
resource group to be up before an application resource groups comes
up.
At startup the order is honored, and the resource groups come up in
the
desired order.
depending on your version, you might need to add:
symmetrical="true"
and
score="INFINITY"
to the ordering constraint
the first should make the resources stop in the reverse order.
the second will make sure that the other two resources will be stopped
if iscsi_resources isn't running
i'd recommend the latest interim build and this document
http://oss.beekhof.net/~beekhof/heartbeat/docs/Ordering-Explained.pdf
In the event of a failover in the storage group I would like the
application groups to go offline while the storage group fails over to
another node, otherwise the applications will crash because they have
lost access to the storage.
The application resource groups do not stop while the storage group
recovers.
If two groups are created, call them resource1 and resource2, and then
an order constraint is created where resource1 before resource2,
should
resource2 go offline during a failover of resource1? In my test setup
they do not.
This is a 5 node non-symmetrical cluster with the storage resource
group
constrained to 2 nodes and the application resource group running on 2
nodes, with the 5th node being the failover target for the other 2
application nodes.
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
