proxmox-mirrors/pve-docs
1
0
Fork 0
mirror of https://git.proxmox.com/git/pve-docs synced 2025-04-29 10:40:45 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

ha-manager: clarify start failure policy

Browse Source 
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@proxmox.com>
This commit is contained in:
Thomas Lamprecht 2016-06-14 17:36:50 +02:00 committed by Dietmar Maurer
parent c9aa5d470e
commit a3189ad1f3
1 changed files with 12 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
ha-manager.adoc
View File

@ -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::