Support for High-Availability mode based on Backends #5
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
armon
added a commit
that referenced
this pull request
Apr 14, 2015
Support for High-Availability mode based on Backends
|
Just my curiosity here...in order to setup HA, I need to unseal all servers? Essentially then you'd have all servers unsealed ready to step up. My question would be, in a lockdown / seal scenario, that'd then mean you'd need to seal all of them separately, correct? |
|
@pearkes Correct on both counts! |
|
Looks great! I'll add some more info the CLI output to relay this information. I think maybe changing |
|
Yeah that might be useful, since then we can provide standby and leader info. Also we may need configuration flags for that advertise address. We can detect a default if consul if being used by asking the agent for the local address. |
Closed
jeffwecan
added a commit
to jeffwecan/vault
that referenced
this pull request
Nov 7, 2018
[NOJIRA] Timeout requests for input and deploys for now
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support for running Vault in a highly-available mode. In addition to a sealed/unsealed state, there is now an active/standby state. Once unsealed, if HA is enabled, the Core goes into a standby state. It waits until it can acquire the global mutex, and then enters the active state allowing operations to be processed. Sealing the core causes an immediate step-down, but otherwise once unsealed, the core will go between standby and active automatically based on lock acquisition.