stop`, which sets the requested state to `stopped`.
NOTE: The HA stack works fully asynchronous and needs to communicate
-with other cluster members. So it takes some seconds unless you see
+with other cluster members. So it takes some seconds until you see
the result of such actions.
To view the current HA resource configuration use:
[NOTE]
Locks are provided by our distributed configuration file system (pmxcfs).
They are used to guarantee that each LRM is active once and working. As a
-LRM only executes actions when it holds its lock we can mark a failed node
+LRM only executes actions when it holds its lock, we can mark a failed node
as fenced if we can acquire its lock. This lets us then recover any failed
HA services securely without any interference from the now unknown failed node.
This all gets supervised by the CRM which holds currently the manager master
[thumbnail="gui-ha-manager-add-group.png"]
-A commom requirement is that a resource should run on a specific
+A common requirement is that a resource should run on a specific
node. Usually the resource is able to run on other nodes, so you can define
an unrestricted group with a single member:
The `nofailback` options is mostly useful to avoid unwanted resource
-movements during administartion tasks. For example, if you need to
+movements during administration tasks. For example, if you need to
migrate a service to a node which hasn't the highest priority in the
group, you need to tell the HA manager to not move this service
instantly back by setting the `nofailback` option.
projects / pve-docs.git / blobdiff