-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
mysql ha lock session expires after session wait_timeout #18582
Labels
Comments
Can you please provide more information about your configuration? Thanks! |
Hi this is my configuration for the mysql backend. Thanks.
|
ffkaka
added a commit
to ffkaka/vault
that referenced
this issue
Jan 18, 2023
…ck lock) hashicorp#18582 * add field "lockConn" which is dedicated for lock * use "lockConn" for monitoring lock(IS_USED_LOC) as well
hi @hsimon-hashicorp |
This was referenced May 9, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
HA with MySQL physical backend
With the MySQL backend, I can see frequent active node changing at every session wait_timeout. So the active node changing period is depending on the configuration of mysql.
(wait_timeout=300sec for test, every cross line means active node switching)
but I want to make less active node switching because every active node switching will cause a bad response for some vault requests in our service. Honestly, I don't expect the active node to change unless the active node gets in trouble. Currently, the session which has been used to acquire the mysql lock will not be used again until it loses the lock. So I think we can use this session for monitoring lock instead of which is doing it using a random session. Therefor the lock session won't get to the wait_timeout and lose lock.The text was updated successfully, but these errors were encountered: