[ClusterLabs] Strange behavior of Resource stickiness

[Klaus Wenninger]

On Tue, May 28, 2024 at 12:34 PM Александр Руденко <a.rudikk at gmail.com>
wrote:

> Andrei, thank you!
>
> I tried to find node's scores and have found location constraints for
> these 3 resources:
>
> pcs constraint
> Location Constraints:
>   Resource: fsmt-28085F00
>     Enabled on:
>       Node: vdc16 (score:INFINITY) (role:Started)
>   Resource: fsmt-41CC55C0
>     Enabled on:
>       Node: vdc16 (score:INFINITY) (role:Started)
>   Resource: fsmt-A7C0E2A0
>     Enabled on:
>       Node: vdc16 (score:INFINITY) (role:Started)
>
> but, I can't understand how these constraints were set. Can it be defined
> by pacemaker in some conditions or it's only manual configuration?
>

Interesting: Didn't have that mail when I just answered you previous.
Anyway - the constraints are probably leftovers from deliberately moving
resources
from ne node to another before using pcs commands.
iirc there is meanwhile a way how pcs removes them automatically.

Klaus


>
> BTW, how can I see the node's score?
>
> вт, 28 мая 2024 г. в 11:59, Andrei Borzenkov <arvidjaar at gmail.com>:
>
>> On Tue, May 28, 2024 at 11:39 AM Александр Руденко <a.rudikk at gmail.com>
>> wrote:
>> >
>> > Hi!
>> >
>> > I can't understand this strange behavior, help me please.
>> >
>> > I have 3 nodes in my cluster, 4 vCPU/8GB RAM each. And about 70 groups,
>> 2 resources in each group. First one resource is our custom resource which
>> configures Linux VRF and second one is systemd unit. Everything works fine.
>> >
>> > We have next defaults:
>> > pcs resource defaults
>> > Meta Attrs: rsc_defaults-meta_attributes
>> >   resource-stickiness=100
>> >
>> > When I shutdown pacemaker service on NODE1, all the resources move to
>> NODE2 and NODE3, it's okay. But when I start pacemaker service on NODE1, 3
>> of 70 groups move back to NODE1.
>> > But I expect that no one resource will be moved back to NODE1.
>> >
>> > I tried to set resource-stickiness=100 exactly for these 3 groups, but
>> it didn't help.
>> >
>> > pcs resource config fsmt-41CC55C0
>> >  Group: fsmt-41CC55C0
>> >   Meta Attrs: resource-stickiness=100
>> > ...
>> >
>> > Why are these 3 resource groups moving back?
>> >
>>
>> Because NODE1 score is higher than NODE2 score + 100. E.g. NODE1 score
>> may be infinity.
>> _______________________________________________
>> Manage your subscription:
>> https://lists.clusterlabs.org/mailman/listinfo/users
>>
>> ClusterLabs home: https://www.clusterlabs.org/
>>
> _______________________________________________
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> ClusterLabs home: https://www.clusterlabs.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20240528/a26a9f3f/attachment-0001.htm>