pveum: Document reserved characters and quoting of LDAP DNs

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

diff --git a/ha-manager.adoc b/ha-manager.adoc
index 710cbca650a80df4d9b7109921722856d3132dd8..ccbb7f83c9f0236b634db95ba6edb8bc90e0d25e 100644 (file)
--- a/ha-manager.adoc
+++ b/ha-manager.adoc
@@ -933,8 +933,9 @@ NOTE: Please do not 'kill' services like `pve-ha-crm`, `pve-ha-lrm` or
 immediate node reboot or even reset.
 
 
-Scheduler Mode
---------------
+[[ha_manager_crs]]
+Cluster Resource Scheduling
+---------------------------
 
 The scheduler mode controls how HA selects nodes for the recovery of a service
 as well as for migrations that are triggered by a shutdown policy. The default
@@ -944,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
@@ -959,18 +956,18 @@ NOTE: There are plans to add modes for (static and dynamic) load-balancing in
 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
-^^^^^^
+~~~~~~
 
-WARNING: The static mode is still a technology preview. It is not recommended to
-use it if you have thousands of HA managed services.
+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
@@ -981,6 +978,11 @@ more, as ideally no node should be overcommitted) and average usage of all nodes
 (to still be able to distinguish in case there already is a more highly
 committed node) are considered.
 
+IMPORTANT: The more services the more possible combinations there are, so it's
+currently not recommended to use it if you have thousands of HA managed
+services.
+
+
 ifdef::manvolnum[]
 include::pve-copyright.adoc[]
 endif::manvolnum[]