-
Notifications
You must be signed in to change notification settings - Fork 102
spKillSessionsForShardMappingLocal: Fix deadlock when the session is already gone #209
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
base: master
Are you sure you want to change the base?
Conversation
|
I see that this project is alive again. Do you plan to merge this PR? Or somehow fix the problem? |
|
I don't have any context into this PR, and I don't see any tests for it (or even how to manually test the PR). Can anyone describe how to test this PR? Is it covered by an existing test? (I am not keen on merging PRs with no tests) |
|
We're also getting this issue in our production environment. It doesn't seem to be an issue in lower environments where there is less activity. Here is the exception and stacktrace |
Fixed deadlock when the kill always returns 6106 forever for the session that is already gone. In this modification it will try to kill the session only once then moving to next in the next round.
Not sure I modified script versioning correctly, but you can see the idea of the fix.
This also probably address some issues mentioned in #166.