From 4aff0037d039c0410bc0a99ef5dcde987898c3cf Mon Sep 17 00:00:00 2001 From: hc-github-team-secure-vault-core <82990506+hc-github-team-secure-vault-core@users.noreply.github.com> Date: Fri, 19 May 2023 16:04:24 -0400 Subject: [PATCH] backport of commit c250c95614bfd3b9cf4389edf7d403b197230309 (#20693) Co-authored-by: Christopher Swenson --- website/content/docs/internals/high-availability.mdx | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/website/content/docs/internals/high-availability.mdx b/website/content/docs/internals/high-availability.mdx index f597b5cdb5..7af93fcc9a 100644 --- a/website/content/docs/internals/high-availability.mdx +++ b/website/content/docs/internals/high-availability.mdx @@ -37,8 +37,7 @@ If a server is in a sealed state, it cannot act as a standby. Servers in a seale # Performance Standby Nodes (Enterprise) -Performance Standby Nodes, like traditional High Availability standby -nodes, service read-only requests from users or applications. +Performance Standby Nodes service read-only requests from users or applications. Read-only requests are requests that do not modify Vault's storage. Vault quickly scales its ability to service these operations, providing a near-linear request-per-second scaling for most scenarios and secrets engines like K/V and Transit. Traffic is distributed across performance standby nodes, allowing clients to scale these IOPS horizontally, and control high traffic workloads.