[ClusterLabs] Antw: [EXT] Re: what is the "best" way to completely shutdown a two‑node cluster ?

Ulrich Windl Ulrich.Windl at rz.uni-regensburg.de
Thu Feb 10 09:10:20 EST 2022


>>> Jehan-Guillaume de Rorthais <jgdr at dalibo.com> schrieb am 10.02.2022 um
10:15 in
Nachricht <20220210101508.768cf643 at karst>:
> On Wed, 9 Feb 2022 17:42:35 +0000 (UTC)
> Strahil Nikolov via Users <users at clusterlabs.org> wrote:
> 
>> If you gracefully shutdown a node ‑ pacemaker will migrate all resources
away
>>  so you need to shut them down simultaneously and all resources should be
>> stopped by the cluster.
>> 
>> Shutting down the nodes would be my choice.
> 
> If you want to gracefully shutdown your cluster, then you can add one
manual
> step to first gracefully stop your resources instead of betting the cluster
> will do the good things.

It's the old discussion: Old HP ServiceGuard had commands to halt a node and
the halt the cluster; pacemaker never had a command to halt the cluster.
IMHO that would be more important than localized messages, for example.

> 
> As far as I remember, there's no way the DC/CRM can orchestrate the whole
> cluster shutdown gracefully in the same transition. So I prefer standing on

> the
> safe side and add one step to my procedure.

Im my simple view of things when the DC can tell one node to stop, why can't
it tell all nodes to stop?

> 
> I even add it with commands like `pcs cluster stop ‑‑all` which tries to
> shutdown all the nodes "kind of" in the same time everywhere. At least, I 
> know
> where my resources were stopped and how they will start. It might be 
> important
> when you deal with eg. permanent promotion scores.
> 
> ++
> _______________________________________________
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users 
> 
> ClusterLabs home: https://www.clusterlabs.org/ 





More information about the Users mailing list