upstream/vault
1
0
Fork 0
mirror of https://github.com/hashicorp/vault.git synced 2026-06-08 16:24:51 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 9

Clarify that Perf Standbys require Consul backend (#5539)

Browse source 
* Clarify that Perf Standbys require Consul backend

* Fixed for line length
This commit is contained in:
Justin Shoffstall 2018-10-25 16:13:44 -04:00 committed by Chris Hoffman
parent a92d999f08
commit 98357621ae
1 changed files with 8 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
website/source/guides/operations/performance-nodes.html.md
View file

@ -20,13 +20,14 @@ _standby_ nodes and simply forward requests to the _active_ node.
![HA Architecture](/img/vault-ha-consul-3.png)
If you are running **_Vault Enterprise_ 0.11** or later, those standby nodes can
handle most read-only requests. For example, performance standbys can handle
encryption/decryption of data using [transit](/docs/secrets/transit/index.html)
keys, GET requests of key/value secrets and other requests that do not change
underlying storage. This can provide considerable improvements in throughput for
traffic of this type, resulting in aggregate performance increase linearly
correlated to the number of performance standby nodes deployed in a cluster.
If you are running **_Vault Enterprise_ 0.11** or later with the Consul storage
backend, those standby nodes can handle most read-only requests. For example,
performance standbys can handle encryption/decryption of data using
[transit](/docs/secrets/transit/index.html) keys, GET requests of key/value
secrets and other requests that do not change underlying storage. This can
provide considerable improvements in throughput for traffic of this type,
resulting in aggregate performance increase linearly correlated to the number
of performance standby nodes deployed in a cluster.
## Reference Materials