[ClusterLabs] Antw: Antw: [EXT] Re: SAP HANA monitor fails ‑ Error performing operation: No such device or address

[Ulrich Windl]

>>> "Ulrich Windl" <Ulrich.Windl at rz.uni-regensburg.de> schrieb am 11.04.2022
um
08:01 in Nachricht <6253C432020000A10004944D at gwsmtp.uni-regensburg.de>:
>>>> Ken Gaillot <kgaillot at redhat.com> schrieb am 08.04.2022 um 15:38 in
> Nachricht
> <7f3a5e59a3b66f520fa549c1151473efbf0fd980.camel at redhat.com>:
> 
> ...
>> I'm not familiar enough with SAP to speak to that side of things, but
>> the behavior after clean‑up is normal. If you don't want resources to
>> go back to their preferred node after a failure is cleaned up, set the
>> resource‑stickiness meta‑attribute to a positive number (either on the
>> resource itself, or in resource defaults if you want it to apply to
>> everything).
> ...
> 
> Unfortunately the value to set for stickiness is some what balck magic:

s/balck/black/

> It seems it does not make a real difference whether you set it to 5, 10, 
> 100,
> or 1000; once grater than 0 it prevents resource migration, even when a

s/grater/greater/

> placement strategy suggests that the placement is non-optimal (e.g. after a
> node restart).

Sorry for the typos; sometimes I think the keyboard (driver) does not like
me... ;-)

> 
> Regards,
> Ulrich
> 
> _______________________________________________
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users 
> 
> ClusterLabs home: https://www.clusterlabs.org/