[ClusterLabs] Antw: [EXT] Pacemaker trades restart for migration on resource parameter change

Ulrich Windl Ulrich.Windl at rz.uni-regensburg.de
Fri Mar 13 03:44:15 EDT 2020

>>> <wferi at niif.hu> schrieb am 13.03.2020 um 08:36 in Nachricht
<19666_1584085000_5E6B3808_19666_1044_1_87imj8vh90.fsf at lant.ki.iif.hu>:
> Hi,
> A user noticed that after changing a non‑reloadable (unique) parameter
> of resource A in our cluster, A wasn't restarted as expected.  On closer
> inspection it turned out that the parameter change was coupled with a
> utilization change as well, which necessitated shuffling resources
> around.  All but a few resources have allow‑migrate set to true.

It won't help you, but I also found it rather difficult to debug issues
related to unresolvable utilization constraints, i.e. there is not good message
when a resource cannot start due to utilization constraints.



More information about the Users mailing list