From a3189ad1f3b3890075744e367789e28f54c2c771 Mon Sep 17 00:00:00 2001 From: Thomas Lamprecht Date: Tue, 14 Jun 2016 17:36:50 +0200 Subject: [PATCH] ha-manager: clarify start failure policy Rename to 'start failure policy' as else it may be confused with recovery after fencing, also derscribe its intend. Signed-off-by: Thomas Lamprecht --- ha-manager.adoc | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/ha-manager.adoc b/ha-manager.adoc index 026d4a4..53ee319 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 ---------------- +Start Failure Policy +--------------------- -There are two service recover policy settings which can be configured +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::