mirror of
				https://github.com/optim-enterprises-bv/vault.git
				synced 2025-10-31 18:48:08 +00:00 
			
		
		
		
	backport of commit c250c95614 (#20693)
				
					
				
			Co-authored-by: Christopher Swenson <christopher.swenson@hashicorp.com>
This commit is contained in:
		 hc-github-team-secure-vault-core
					hc-github-team-secure-vault-core
				
			
				
					committed by
					
						 GitHub
						GitHub
					
				
			
			
				
	
			
			
			 GitHub
						GitHub
					
				
			
						parent
						
							191712ea2f
						
					
				
				
					commit
					4aff0037d0
				
			| @@ -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 (Enterprise) | ||||||
|  |  | ||||||
| Performance Standby Nodes, like traditional High Availability standby | Performance Standby Nodes service read-only requests from users or applications. | ||||||
| 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, | 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. | 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. | ||||||
|  |  | ||||||
|   | |||||||
		Reference in New Issue
	
	Block a user