[Linux-HA] Constraints when a resource (group) goes down?

[Andrew Beekhof]

On 11/2/06, Hildebrand, Nils, 232 <Nils.Hildebrand at bamf.bund.de> wrote:
> Hi,
>
> I have set up a simple two-node-cluster. For a proof of concept I just use
> dummy resources for the beginning (see attached cib-file).
>
> Following dependencies should be met ALL TIMES:
>
> - Group "Redaktion" should be first,
> - Group "Master" should be next,
> - Group "Slave" should be last,
> - Group "Master" and "Slave" are never active on the same node.
>
> With the attached cib this works pretty well (on failover/failback
> situations).

you might want to also assign priorities so they are always processed
in this order.

>
> Next Test:
> When all (or certain) master resources fail the expected behaviour would
> have been that the slave-group gets stopped, master restarts, slave starts.

for this you need the restart_type resource attribute:
     http://www.linux-ha.org/v2/dtd1.0/annotated

>
> I simulate the failure of resources by deleting the resource-files located
> at
>   /var/run/heartbeat/rsctmp
>
> But now the following happens:
> Whenever a resource from RG "Master" goes down, it gets restarted - even if
> ALL resources of the same resource group are down.
>
> To me this seems to be a bug, since the constraint "Slave after Master" is
> not being met.
>
> Is there any way around this problem?
>
>
> Kind regards, Nils
>
>
>
> _______________________________________________
> Linux-HA mailing list
> Linux-HA at lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>
>
>