From 8dcad10c19b0eae1b32860930ff6013e407453fd Mon Sep 17 00:00:00 2001 From: Thomas Lamprecht Date: Fri, 27 Oct 2023 16:06:30 +0200 Subject: [PATCH] ha: maintenance mode: fix grammar and reword This was a bit complex while leaving out some key info, like that HA groups also play into the target selection, not only CRS. Try to improve on that. Signed-off-by: Thomas Lamprecht --- ha-manager.adoc | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/ha-manager.adoc b/ha-manager.adoc index 7f1ba3d..8390782 100644 --- a/ha-manager.adoc +++ b/ha-manager.adoc @@ -853,12 +853,15 @@ The HA stack can support you mainly in two types of maintenance: Maintenance Mode ~~~~~~~~~~~~~~~~ -Enabling the manual maintenance mode will mark the node as unavailable for -operation, this in turn will migrate away all HA services to other nodes, which -are selected through the configured cluster resource scheduler (CRS) mode. -During migration the original node will be recorded, so that the service can be -moved back to to that node as soon as the maintenance mode is disabled, and it -becomes online again. +You can use the manual maintenance mode to mark the node as unavailable for HA +operation, prompting all services managed by HA to migrate to other nodes. + +The target nodes for these migrations are selected from the other currently +available nodes, and determined by the HA group configuration and the configured +cluster resource scheduler (CRS) mode. +During each migration, the original node will be recorded in the HA managers' +state, so that the service can be moved back again automatically once the +maintenance mode is disabled and the node is back online. Currently you can enabled or disable the maintenance mode using the ha-manager CLI tool.