[Pacemaker] Infinite fail-count and migration-threshold after node fail-back

[Pavlos Parissis]

On 11 November 2010 13:04, Dan Frincu <dfrincu at streamwide.ro> wrote:
> Hi,
>
> Andrew Beekhof wrote:
>
> On Mon, Oct 11, 2010 at 9:40 AM, Dan Frincu <dfrincu at streamwide.ro> wrote:
>
>
> Hi all,
>
> I've managed to make this setup work, basically the issue with a
> symmetric-cluster="false" and specifying the resources' location manually
> means that the resources will always obey the location constraint, and (as
> far as I could see) disregard the rsc_defaults resource-stickiness values.
>
>
> This definitely should not be the case.
> Possibly your stickiness setting is being eclipsed by the combination
> of the location constraint scores.
> Try INFINITY instead.
>
>
>
> I understand your point and I believe also this to be the case, however I've
> noticed that by specifying symmetric-cluster="false" for each resource I
> need to add 2 location constraints, which overcrowds the config, and if I
> want (and hope) to go to a config with multiple servers and resources, each
> with specific rules, then also adding location constraints for each resource
> is an overhead which I'd rather not include, if possible.