Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ha mode - etcd v3 - standby never becomes active when the active goes down #2540

Closed
raoofm opened this issue Mar 28, 2017 · 3 comments
Closed

Comments

@raoofm
Copy link
Contributor

raoofm commented Mar 28, 2017

vault 0.7.0
etcd 3.1.3

when /v1/sys/step-down is called on the active node then the standby replaces it as active but if you actually kill the active node then the standby nodes never takes over.

Expected behavior is
If you kill Vault without letting it release the lock, a standby node will not be able to take over until the lock's timeout period has expired. This is backend-specific but could be ten seconds or more.

I checked etcdv3 backend and it shows 15s but it doesn't seem to work.

In a real world scenario, HA mode is used for sudden loss of a server and not for planned step-down (used only during upgrades).

@raoofm
Copy link
Contributor Author

raoofm commented Mar 28, 2017

@jefferai @xiang90 ?

@jefferai
Copy link
Member

This should be fixed by #2526

@raoofm
Copy link
Contributor Author

raoofm commented Mar 28, 2017

great, thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants