[[chapter-ha-manager]] ifdef::manvolnum[] PVE({manvolnum}) ================ include::attributes.txt[] NAME ---- ha-manager - Proxmox VE HA Manager SYNOPSYS -------- include::ha-manager.1-synopsis.adoc[] DESCRIPTION ----------- endif::manvolnum[] ifndef::manvolnum[] High Availability ================= include::attributes.txt[] endif::manvolnum[] Our modern society depends heavily on information provided by computers over the network. Mobile devices amplified that dependency, because people can access the network any time from anywhere. If you provide such services, it is very important that they are available most of the time. We can mathematically define the availability as the ratio of (A) the total time a service is capable of being used during a given interval to (B) the length of the interval. It is normally expressed as a percentage of uptime in a given year. .Availability - Downtime per Year [width="60%",cols="/lrm_status'. There the CRM may collect it and let its state machine - respective the commands output - act on it. The actions on each service between CRM and LRM are normally always synced. This means that the CRM requests a state uniquely marked by an UID, the LRM then executes this action *one time* and writes back the result, also identifiable by the same UID. This is needed so that the LRM does not executes an outdated command. With the exception of the 'stop' and the 'error' command, those two do not depend on the result produce and are executed always in the case of the stopped state and once in the case of the error state. .Read the Logs [NOTE] The HA Stack logs every action it makes. This helps to understand what and also why something happens in the cluster. Here its important to see what both daemons, the LRM and the CRM, did. You may use `journalctl -u pve-ha-lrm` on the node(s) where the service is and the same command for the pve-ha-crm on the node which is the current master. Cluster Resource Manager ~~~~~~~~~~~~~~~~~~~~~~~~ The cluster resource manager ('pve-ha-crm') starts on each node and waits there for the manager lock, which can only be held by one node at a time. The node which successfully acquires the manager lock gets promoted to the CRM master. It can be in three states: TODO * *wait for agent lock*: the LRM waits for our exclusive lock. This is also used as idle sate if no service is configured * *active*: the LRM holds its exclusive lock and has services configured * *lost agent lock*: the LRM lost its lock, this means a failure happened and quorum was lost. It main task is to manage the services which are configured to be highly available and try to get always bring them in the wanted state, e.g.: a enabled service will be started if its not running, if it crashes it will be started again. Thus it dictates the LRM the wanted actions. When an node leaves the cluster quorum, its state changes to unknown. If the current CRM then can secure the failed nodes lock, the services will be 'stolen' and restarted on another node. When a cluster member determines that it is no longer in the cluster quorum, the LRM waits for a new quorum to form. As long as there is no quorum the node cannot reset the watchdog. This will trigger a reboot after 60 seconds. Configuration ------------- The HA stack is well integrated int the Proxmox VE API2. So, for example, HA can be configured via 'ha-manager' or the PVE web interface, which both provide an easy to use tool. The resource configuration file can be located at '/etc/pve/ha/resources.cfg' and the group configuration file at '/etc/pve/ha/groups.cfg'. Use the provided tools to make changes, there shouldn't be any need to edit them manually. Node Power Status ----------------- If a node needs maintenance you should migrate and or relocate all services which are required to run always on another node first. After that you can stop the LRM and CRM services. But note that the watchdog triggers if you stop it with active services. Fencing ------- What Is Fencing ~~~~~~~~~~~~~~~ Fencing secures that on a node failure the dangerous node gets will be rendered unable to do any damage and that no resource runs twice when it gets recovered from the failed node. Configure Hardware Watchdog ~~~~~~~~~~~~~~~~~~~~~~~~~~~ By default all watchdog modules are blocked for security reasons as they are like a loaded gun if not correctly initialized. If you have a hardware watchdog available remove its module from the blacklist and restart 'the watchdog-mux' service. Groups ------ A group is a collection of cluster nodes which a service may be bound to. Group Settings ~~~~~~~~~~~~~~ nodes:: list of group node members restricted:: resources bound to this group may only run on nodes defined by the group. If no group node member is available the resource will be placed in the stopped state. nofailback:: 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 specific for each resource. max_restart:: maximal number of tries to restart an failed service on the actual node. The default is set to one. max_relocate:: maximal number of tries to relocate the service to a different node. A relocate only happens after the max_restart value is exceeded on the actual node. The default is set to one. Note that the relocate count state will only reset to zero when the service had at least one successful start. That means if a service is re-enabled without fixing the error only the restart policy gets repeated. Error Recovery -------------- If after all tries the service state could not be recovered it gets placed in an error state. In this state the service won't get touched by the HA stack anymore. To recover from this state you should follow these steps: * bring the resource back into an safe and consistent state (e.g: killing its process) * disable the ha resource to place it in an stopped state * fix the error which led to this failures * *after* you fixed all errors you may enable the service again Service Operations ------------------ This are how the basic user-initiated service operations (via 'ha-manager') work. enable:: the service will be started by the LRM if not already running. disable:: the service will be stopped by the LRM if running. migrate/relocate:: the service will be relocated (live) to another node. remove:: the service will be removed from the HA managed resource list. Its current state will not be touched. start/stop:: start and stop commands can be issued to the resource specific tools (like 'qm' or 'pct'), they will forward the request to the 'ha-manager' which then will execute the action and set the resulting service state (enabled, disabled). Service States -------------- stopped:: Service is stopped (confirmed by LRM) request_stop:: Service should be stopped. Waiting for confirmation from LRM. started:: Service is active an LRM should start it ASAP if not already running. fence:: Wait for node fencing (service node is not inside quorate cluster partition). freeze:: Do not touch the service state. We use this state while we reboot a node, or when we restart the LRM daemon. migrate:: Migrate service (live) to other node. error:: Service disabled because of LRM errors. Needs manual intervention. ifdef::manvolnum[] include::pve-copyright.adoc[] endif::manvolnum[]