[fix] add checks for stopped queries #8097
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
CATEGORY
Choose one
SUMMARY
When a user tries to stop a query, very occasionally, the action fails and the query still runs to completion. The issue isn't user-facing, but errors in the backend show that there is some kind of lock wait timeout issue.
Unknown if it is possible to completely prevent these, and the issue isn't really user-facing, but I added some tweaks to hopefully prevent a few of these conflicts.
commit()
after setting the initial query status toRUNNING
TEST PLAN
Tox passes.
I didn't write a test because it is pretty hard to reproduce this error - seems like a rare timing thing. These changes are mostly for safety and shouldn't affect behavior of anything.
REVIEWERS
@etr2460