On Thu, 10 Feb 2022 22:15:07 +0800 Roger Zhou via Users <users@clusterlabs.org> wrote:
> > On 2/9/22 17:46, Lentes, Bernd wrote: > > > > > > ----- On Feb 7, 2022, at 4:13 PM, Jehan-Guillaume de Rorthais > > j...@dalibo.com wrote: > > > >> On Mon, 7 Feb 2022 14:24:44 +0100 (CET) > >> "Lentes, Bernd" <bernd.len...@helmholtz-muenchen.de> wrote: > >> > >>> Hi, > >>> > >>> i'm currently changing a bit in my cluster because i realized that my > >>> configuration for a power outtage didn't work as i expected. My idea is > >>> currently: > >>> - first stop about 20 VirtualDomains, which are my services. This will > >>> surely takes some minutes. I'm thinking of stopping each with a time > >>> difference of about 20 seconds for not getting to much IO load. and then > >>> ... > > This part is tricky. At one hand, it is good thinking to throttle IO load. > > On the other hand, as Jehan and Ulrich mentioned, `crm resource stop <rsc>` > introduces "target‑role=Stopped" for each VirtualDomain, and have to do `crm > resource start <rsc>` to changed it back to "target‑role=Started" to start > them after the power outage. I wonder if after the cluster shutdown complete, the target-role=Stopped could be removed/edited offline with eg. crmadmin? That would make VirtualDomain startable on boot. I suppose this would not be that simple as it would require to update it on all nodes, taking care of the CIB version, hash, etc... But maybe some tooling could take care of this? Last, if Bernd need to stop gracefully the VirtualDomain paying attention to the I/O load, maybe he doesn't want them start automatically on boot for the exact same reason anyway? ++ _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
