On 7/13/07, Lars Marowsky-Bree <[EMAIL PROTECTED]> wrote:
On 2007-07-13T17:06:27, Maxim Veksler <[EMAIL PROTECTED]> wrote:
> Hello list,
>
> I have two nodes (rnd-dev1, rnd-dev2) running RH4 with CentOS based
> rpm install of heartbeat 2.0.7
2.0.7 is ancient. Do not use it any longer. Please, update.
> I'm seeing a problem where heartbeat prefers to always run resources
> on node2, even when I deliberately make them return 1 on monitor
> action.
>
> The only scenario where heartbeat chooses to run them on node1 is when
> I stop heartbeat on node2, if I start heartbeat again on node2 the
> resources will migrate there again (and continue failing).
>
> Have I configured something wrong in the cib? (attached below)
Yes. monitor failures do not automatically imply that the node is
broken, just that the resource needs to be restarted. You need
resource_stickiness and resource_failure_stickiness, both of which are
documented on the website.
Thank you, this is a bit OT but you guys could use some help with the
documentation IMOH. From searching for "resource_failure_stickiness"
on site:linux-ha.org only the forth option leads to a somewhat
relevant issue, which is V2 FAQ. Should I be looking at a different
page to educate myself on the subject ?
Thank you for helping Lars.
Regards,
Lars
--
Teamlead Kernel, SuSE Labs, Research and Development
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
--
Cheers,
Maxim Veksler
"Free as in Freedom" - Do u GNU ?
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
