upstream/vault
1
0
Fork 0
mirror of https://github.com/hashicorp/vault.git synced 2026-05-28 04:10:44 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

Update health.mdx (#26264)

Browse source 
To address the confusion on 472 status code, in addition to explain in rare occasions when a 429 could be returned.
This commit is contained in:
Jason Peng 2024-04-22 15:45:20 -07:00 committed by GitHub
parent 069975413f
commit 5f4e53e5a2
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 5 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
website/content/api-docs/system/health.mdx
View file

@ -25,11 +25,15 @@ The default status codes are:
- `200` if initialized, unsealed, and active
- `429` if unsealed and standby
- `472` if disaster recovery mode replication secondary and active
- `472` if disaster recovery secondary (both active and standby nodes within the DR secondary)
- `473` if performance standby
- `501` if not initialized
- `503` if sealed
<Note>
In rare occasions such as during cluster instability, a node may return 429 even when it was part of a DR secondary (472) or a perf-standby (473). When configuring a Load Balancer based on health status API, it's important to recognize that a 429 indicates a standby node that doesn't process the request itself, read or write.
</Note>
### Parameters
- `standbyok` `(bool: false)` – Specifies if being a standby should still return