On Fri, 11 Feb 2022 08:07:33 +0100 "Ulrich Windl" <ulrich.wi...@rz.uni-regensburg.de> wrote:
> >> Jehan-Guillaume de Rorthais <j...@dalibo.com> schrieb am 10.02.2022 um > 16:40 in Nachricht <20220210164000.2e395a37@karst>: > > ... > > 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. > > It has also discussed before: "restart" is implemented by "first change role > to stopped, then change role to started". > If the performing node is fenced due to a stop failure, the resource is never > started. > So what's needed is a transient (i.e.: not saved in CIB) "restart" operation, > that reverts to the previous state (started, most likely) if the the node > performing it dies. > Now transfer this to "stop-all-resources": The role attribute in the CIB would > never be changed, but maybe just all the LRMs would stop their resources, > eventually shutting down and when the node comes up again, the previous state > will be re-established. Nice, indeed. > > ... > > 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? > > But you can limit the number of concurrent invocations and migrations, right? > Unfortunately I cannot remember the parameter. I suppose you are talking about cluster option "batch-limit"? But then, this would have to be set to eg. "batch-limit=1" (?) only during shutdown/startup action, to avoid slowing down cluster action during normal operation. ++ _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/