mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-06 06:46:26 +01:00
39 lines
1.2 KiB
Plaintext
39 lines
1.2 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * scalability_and_performance/recommended-performance-scale-practices/recommended-etcd-practices.adoc
|
|
|
|
:_mod-docs-content-type: CONCEPT
|
|
[id="etcd-node-scaling_{context}"]
|
|
= Node scaling for etcd
|
|
|
|
In general, clusters must have 3 control plane nodes. However, if your cluster is installed on a bare metal platform, you can scale a cluster up to 5 nodes as a post-installation task. For example, to scale from 3 to 4 nodes after installation, you can add a host and install it as a control plane node. Then, the etcd Operator scales accordingly to account for the additional node.
|
|
|
|
Scaling to 4-node or 5-node clusters is available only on bare metal platforms.
|
|
|
|
For more information about how to scale from 3 to 4 nodes by using the Assisted Installer, see "Adding hosts with the API" and "Installing a primary control plane node on a healthy cluster".
|
|
|
|
The following table shows failure tolerance for clusters of different sizes:
|
|
|
|
.Failure tolerances by cluster size
|
|
[%autowidth]
|
|
|===
|
|
|Cluster size |Majority |Failure tolerance
|
|
|
|
|1 node
|
|
|1
|
|
|0
|
|
|
|
|3 nodes
|
|
|2
|
|
|1
|
|
|
|
|4 nodes
|
|
|3
|
|
|1
|
|
|
|
|5 nodes
|
|
|3
|
|
|2
|
|
|===
|
|
|
|
For more information about recovering from quorum loss, see "Restoring to a previous cluster state". |