mirror of
https://github.com/optim-enterprises-bv/vault.git
synced 2025-11-02 03:27:54 +00:00
docs/stepdown-clarification (#12077)
This commit is contained in:
@@ -8,11 +8,14 @@ description: |-
|
||||
|
||||
# operator step-down
|
||||
|
||||
The `operator step-down` forces the Vault server at the given address to step
|
||||
down from active duty. 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 `operator step-down` forces the active Vault node within an [HA cluster](/docs/concepts/ha)
|
||||
to step down from active duty. When executed against a non-active node, i.e. a
|
||||
standby or [performance standby](/docs/enterprise/performance-standby) node,
|
||||
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.
|
||||
|
||||
## Examples
|
||||
|
||||
|
||||
Reference in New Issue
Block a user