>>> Ken Gaillot <[email protected]> schrieb am 27.02.2020 um 23:43 in >>> Nachricht <[email protected]>:
[...] > >> 2. Resources/groups are stopped (target-role=stopped) >> 3. Node exits the cluster cleanly when no resources are running any >> more >> 4. The node rejoins the cluster after the reboot >> 5. A positive (on the rebooted node) & negative (ban on the rest of >> the nodes) constraints are created for the marked in step 1 >> resources >> 6. target-role is set back to started and the resources are back >> and running >> 7. When each resource group (or standalone resource) is back online >> - the mark in step 1 is removed and any location >> constraints (cli-ban & cli-prefer) are removed for the >> resource/group. > > Exactly, that's effectively what happens. May I ask how robust the mechanism will be? For example if you do a "resource restart" there are two target roles (each made persistent): stopped and started. If the node performing the operation is fenced (we had that a few times). The resources may remain "stopped" until started manually again. I see a similar issue with this mechanism. [...] _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
