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

[Andrew Beekhof]

It looks like you've hit a bug :-(

Seems the restart isn't propagated between groups.

While i fix it, you can work around it by changing:
       <rsc_order id="order_Live" from="Slave" type="after" to="Master"/>
       <rsc_order id="order_Redaktion" from="Master" type="after"
to="Redaktion"/>

to:
       <rsc_order id="order_Live" from="resource_VIP2" type="after"
to="Master"/>
       <rsc_order id="order_Redaktion" from="resource_VIP1"
type="after" to="Redaktion"/>

On 1/18/07, Hildebrand, Nils, 232 <Nils.Hildebrand at bamf.bund.de> wrote:
> Hi Andrew,
>
> sorry for the late answer - I had too many concurrent projects...
>
> > [...]
> > you're replacing the existing restart_type="#default" entry
> > in all the groups?
>
> That's what I did.
>
> > if this is what you've done, can you send me the result of
> >    cibadmin -Q
> > from your cluster when its running please?
>
> See attachement. Thanks for your help in advance.
>
> > with that i'll be able to simulate various failures.
>
> Try to fail a resource in "Master". This should also restart the
> "Slave".
>
> In "Redaktion" this should drive down "Slave" then "Master" then start
> "Master" then "Slave".
>
> > if you want it restarted (not sure why since its of type
> > Dummy), then put it after RedWeb in the group.
>
> This whole configuration is just a simulation of the real thing.
>
> For the real Cluster I will use either init-scripts for the
> corresponding resources or convert them to ocf-scripts.
>
> > [...]
> > > I simulate the failure of resources by deleting the resource-files
> located at
> > >   /var/run/heartbeat/rsctmp [...]
>
> 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
>
>
>