-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Don't exit just because we think there was a possible deadlock #21342
Don't exit just because we think there was a possible deadlock #21342
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense to me, we don't want to be crashing Vault for users because of potential deadlocks.
I'm not too sure how we could write an elegant test for this behaviour, since we'd need to wait for 30s, but this is something that our existing tests missed. It's something we should think about adding some kinds of tests for, at least.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I attempted to verify that this probably does what we expect I didn't test manually but based on reading the source code for the library it does indeed seem to be the change we want.
I think this looks like a less risky position to take for now. We can decide later based on occurences of the log messages whether it would be better to allow users to opt in/out of the crash behaviour and/or modify the timeout.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Forgot to approve
Fixes #21338