qm: IO-Thread: rework and add a bit more context

[pve-docs.git] / ha-manager.adoc

diff --git a/ha-manager.adoc b/ha-manager.adoc
index 17e890065fc102276a856da61437167f081c581b..ccbb7f83c9f0236b634db95ba6edb8bc90e0d25e 100644 (file)
--- a/ha-manager.adoc
+++ b/ha-manager.adoc
@@ -945,12 +945,8 @@ mode is `basic`, you can change it in `datacenter.cfg`:
 crs: ha=static
 ----
 
-The change will be in effect when a new master takes over. This can be triggered
-by executing the following on the current master's node:
-
-----
-systemctl reload-or-restart pve-ha-crm.service
-----
+The change will be in effect starting with the next manager round (after a few
+seconds).
 
 For each service that needs to be recovered or migrated, the scheduler
 iteratively chooses the best node among the nodes with the highest priority in
@@ -962,15 +958,16 @@ the future.
 Basic
 ~~~~~
 
-The number of active HA serivces on each node is used to choose a recovery node.
+The number of active HA services on each node is used to choose a recovery node.
+Non-HA-managed services are currently not counted.
 
 Static
 ~~~~~~
 
 IMPORTANT: The static mode is still a technology preview.
 
-Static usage information from HA serivces on each node is used to choose a
-recovery node.
+Static usage information from HA services on each node is used to choose a
+recovery node. Usage of non-HA-managed services is currently not considered.
 
 For this selection, each node in turn is considered as if the service was
 already running on it, using CPU and memory usage from the associated guest