[pve-devel] [PATCH v2 docs] ha-manager: clarify start failure policy

Thomas Lamprecht t.lamprecht at proxmox.com
Tue Jun 14 17:36:50 CEST 2016


Rename to 'start failure policy' as else it may be confused with
recovery after fencing, also derscribe its intend.

Signed-off-by: Thomas Lamprecht <t.lamprecht at proxmox.com>
---

Yes, much better title for what it is, thanks!

changes since v1:
* s/Start Recovery Policy/Start Failure Policy/
* small rewording

 ha-manager.adoc | 17 +++++++++++++----
 1 file changed, 13 insertions(+), 4 deletions(-)

diff --git a/ha-manager.adoc b/ha-manager.adoc
index 2cad06c..afb27ce 100644
--- a/ha-manager.adoc
+++ b/ha-manager.adoc
@@ -378,10 +378,19 @@ the resource won't automatically fail back when a more preferred node
 (re)joins the cluster.
 
 
-Recovery Policy
----------------
-
-There are two service recover policy settings which can be configured
+Start Failure Policy
+---------------------
+
+The start failure policy comes in effect if a service failed to start on a
+node once ore more times. It can be used to configure how often a restart
+should be triggered on the same node and how often a service should be
+relocated so that it gets a try to be started on another node.
+The aim of this policy is to circumvent temporary unavailability of shared
+resources on a specific node. For example, if a shared storage isn't available
+on a quorate node anymore, e.g. network problems, but still on other nodes,
+the relocate policy allows then that the service gets started nonetheless.
+
+There are two service start recover policy settings which can be configured
 specific for each resource.
 
 max_restart::
-- 
2.1.4




More information about the pve-devel mailing list