On Wed, 9 Feb 2022 10:46:30 +0100 (CET) "Lentes, Bernd" <bernd.len...@helmholtz-muenchen.de> 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 > >> ... > >> - how to stop the other resources ? > > > > I would set cluster option "stop-all-resources" so all remaining resources > > are stopped gracefully by the cluster. > > > > Then you can stop both nodes using eg. "crm cluster stop". > > > > On restart, after both nodes are up and joined to the cluster, you can set > > "stop-all-resources=false", then start your VirtualDomains. > > Aren't the VirtualDomains already started by "stop-all-resources=false" ? I'm not sure how "crm resource stop <id>" actually stop a resource. I thought it would set "target-role=Stopped", but I might be wrong. If "crm resource stop" actually use "target-role=Stopped", I believe the resources would not start automatically after setting "stop-all-resources=false". ++ _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/