Update integrated-storage.mdx (#18581)

* Update integrated-storage.mdx

The old paragraph "The recommended deployment is either 3 or 5 servers." should match the "Minimums & Scaling" purpose from below.
It also reaffirms that, in a PRODUCTION environment,  a number of 5 nodes are the minimum requirement.

A rewording is also necessary: "The recommended deployment consists in a minimum of 5 or more of servers that are odd in their total (5, 7, etc)."

* Update website/content/docs/internals/integrated-storage.mdx

Co-authored-by: Yoko Hyakuna <yoko@hashicorp.com>

Co-authored-by: Yoko Hyakuna <yoko@hashicorp.com>
This commit is contained in:
Florin Cătălin Țiucra-Popa 2023-01-04 13:43:05 +01:00 committed by GitHub
parent dcc4c031cc
commit 308c726d4d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -197,7 +197,7 @@ close to the leader before adding additional nodes. Raft indexes are visible via
### Deployment Table
Below is a table that shows quorum size and failure tolerance for various
cluster sizes. The recommended deployment is either 3 or 5 servers. A single
cluster sizes. The recommended deployment consists of a minimum of 5 or more servers that are odd in their total (5, 7, etc). A single
server deployment is _**highly**_ discouraged as data loss is inevitable in a
failure scenario.
@ -272,4 +272,4 @@ any practises that compromise that.
Scaling clusters up or down in pairs with 2 nodes each time also has the added
advantage of avoiding even numbers and it is always recommended to
allow for an odd number of total voters in any cluster.
allow for an odd number of total voters in any cluster.