proxmox-mirrors/pve-docs
1
0
Fork 0
mirror of https://git.proxmox.com/git/pve-docs synced 2025-08-14 12:30:34 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Fix typos in ha-manager.adoc

Browse Source 
Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
This commit is contained in:
Fabian Ebner 2019-09-02 11:19:50 +02:00 committed by Thomas Lamprecht
parent 7420d3f101
commit d5c3a54af9
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
ha-manager.adoc
View File

@ -100,7 +100,7 @@ carefully calculate the benefits, and compare with those additional
costs. costs.
TIP: Increasing availability from 99% to 99.9% is relatively TIP: Increasing availability from 99% to 99.9% is relatively
simply. But increasing availability from 99.9999% to 99.99999% is very simple. But increasing availability from 99.9999% to 99.99999% is very
hard and costly. `ha-manager` has typical error detection and failover hard and costly. `ha-manager` has typical error detection and failover
times of about 2 minutes, so you can get no more than 99.999% times of about 2 minutes, so you can get no more than 99.999%
availability. availability.
@ -761,7 +761,7 @@ specific for each resource.
max_restart:: max_restart::
Maximum number of tries to restart an failed service on the actual Maximum number of tries to restart a failed service on the actual
node. The default is set to one. node. The default is set to one.
max_relocate:: max_relocate::
@ -809,9 +809,9 @@ Package Updates
When updating the ha-manager you should do one node after the other, never When updating the ha-manager you should do one node after the other, never
all at once for various reasons. First, while we test our software all at once for various reasons. First, while we test our software
thoughtfully, a bug affecting your specific setup cannot totally be ruled out. thoughtfully, a bug affecting your specific setup cannot totally be ruled out.
Upgrading one node after the other and checking the functionality of each node Updating one node after the other and checking the functionality of each node
after finishing the update helps to recover from an eventual problems, while after finishing the update helps to recover from eventual problems, while
updating all could render you in a broken cluster state and is generally not updating all at once could result in a broken cluster and is generally not
good practice. good practice.
Also, the {pve} HA stack uses a request acknowledge protocol to perform Also, the {pve} HA stack uses a request acknowledge protocol to perform