scottk/vault
1
0
Fork 0
mirror of https://github.com/optim-enterprises-bv/vault.git synced 2025-10-29 17:52:32 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update step-down.mdx (#21495)

Browse Source 
Updating the vault leader step down documentation to include some extra info about possible failed requests during leader step down

* Add changelog.txt
* Update website/content/docs/commands/operator/step-down.mdx

Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>
This commit is contained in:
Eoin
2023-08-14 23:25:39 +01:00
committed by GitHub
parent 0998226dc7
commit 718540a632
2 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
changelog/21495.txt Normal file
View File

@@ -0,0 +1,3 @@
```release-note:improvement
website/docs: Updating operator step-down docs to include info about possible failed requests during leader step down.
```

3
website/content/docs/commands/operator/step-down.mdx
View File

@@ -15,7 +15,8 @@ the request will be forwarded to the active node. While the
affected node will have a delay before attempting to acquire
the leader lock again, if no other Vault nodes acquire the
lock beforehand, it is possible for the same node to re-acquire
the lock and become active again.
the lock and become active again. Due to the locking architecture, there may be a period of time
before another node grabs the lock and finishes transitioning to active operation where the cluster has no active node. During the period where none of the nodes are active, forwarding of requests to the leader node will fail.
## Examples