mirrors/vault
1
0
Fork 0
mirror of https://github.com/hashicorp/vault.git synced 2025-11-14 15:21:11 +01:00
Code Issues Projects Releases Wiki Activity

Update step-down.mdx to describe behavior against non-active nodes (#23657)

Browse Source 
* Update step-down.mdx to describe behavior against non-active nodes

Behavior changed in Vault 1.9:
https://developer.hashicorp.com/vault/docs/v1.9.x/commands/operator/step-down
This commit is contained in:
Brian Scholer 2023-10-18 22:33:46 -04:00 committed by GitHub
parent b74bb26310
commit a0a150b7f1
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
website/content/api-docs/system/step-down.mdx
View File

@ -12,8 +12,12 @@ The `/sys/step-down` endpoint causes the node to give up active status.
## Step down leader ## Step down leader
This endpoint forces the node to give up active status. If the node does not The step-down endpoint forces nodes to give up "active" status. If you
have active status, this endpoint does nothing. Note that the node will sleep call the endpoint against a non-active node, for example, a DR or
performance standby node, Vault forwards the request to the active
node.
Note that the node will sleep
for ten seconds before attempting to grab the active lock again, but if no for ten seconds before attempting to grab the active lock again, but if no
standby nodes grab the active lock in the interim, the same node may become the standby nodes grab the active lock in the interim, the same node may become the
active node again. Requires a token with `root` policy or `sudo` capability on active node again. Requires a token with `root` policy or `sudo` capability on