-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
*: make Backoff perceive the Killed flag to fix MAX_EXECUTION_TIME #14552
Conversation
Previously we check the killed flag in each executor.Next() call. But if the query current executing Backoff(), we can't terminate the query.
CI fixed in #14554 |
/run-all-tests |
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.
LGTM
there is a race at |
hi @tiancaiamao , would you please update the release note in your PR description? Thanks. |
/run-all-tests |
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.
LGTM
/merge |
/run-all-tests |
cherry pick to release-3.0 failed |
It seems that, not for sure, we failed to cherry-pick this commit to release-3.0. Please comment '/run-cherry-picker' to try to trigger the cherry-picker if we did fail to cherry-pick this commit before. @tiancaiamao PTAL. |
What problem does this PR solve?
Previously we check the killed flag in each executor.Next() call, but if the query current executing Backoff(), we can't terminate the query.
In some cases such as TiKV is crash/recovering, the backoff would last for a long time.
And kill the query doesn't work because the killed flag is not checked during backoff.
Similar issue: #12852
What is changed and how it works?
Pass the
killed
flag tobackoffer
and check the value during backoff.Check List
Tests
Release note
MAX_EXECUTION_TIME
doesn't take effect in some cases