openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-06 15:46:57 +01:00
Code Issues Releases Activity

modules/master-node-sizing: Fix "at least" to "at most" typo

Browse Source 
The goal is to have underutilized nodes with space for workloads to be
squeezed while nodes are being rebooted.  The typo is from 7eb9504406
(Recommendation around master node sizing to handle upgrades,
2021-05-06, #32230).
This commit is contained in:
W. Trevor King
2021-07-06 10:47:51 -07:00
parent d098db9888
commit 4c7a9552b8
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
modules/master-node-sizing.adoc
View File

@@ -40,7 +40,7 @@ The control plane node resource requirements depend on the number of nodes in th
|===
On a cluster with three masters or control plane nodes, the CPU and memory usage will spike up when one of the nodes is stopped, rebooted or fails because the remaining two nodes must handle the load in order to be highly available. This is also expected during upgrades because the masters are cordoned, drained, and rebooted serially to apply the operating system updates, as well as the control plane Operators update. To avoid cascading failures on large and dense clusters, keep the overall resource usage on the master nodes to at least half of all available capacity to handle the resource usage spikes. Increase the CPU and memory on the master nodes accordingly.
On a cluster with three masters or control plane nodes, the CPU and memory usage will spike up when one of the nodes is stopped, rebooted or fails because the remaining two nodes must handle the load in order to be highly available. This is also expected during upgrades because the masters are cordoned, drained, and rebooted serially to apply the operating system updates, as well as the control plane Operators update. To avoid cascading failures on large and dense clusters, keep the overall resource usage on the master nodes to at most half of all available capacity to handle the resource usage spikes. Increase the CPU and memory on the master nodes accordingly.
[IMPORTANT]
====