[BugFix] fix query timeout behavior when using query queue (backport #53677) #53726
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.
Why I'm doing:
For a particular case that a query takes hundreds of seconds in the optimizer then pend in the query queue:
query_queue_timeout
is not changed, since that pending request received a cancel requestWhat I'm doing:
command start
, instead of the time when create slotCancellationException
Fixes #issue
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist:
Bugfix cherry-pick branch check:
This is an automatic backport of pull request [BugFix] fix query timeout behavior when using query queue #53677 done by Mergify.
Why I'm doing:
For a particular case that a query takes hundreds of seconds in the optimizer then pend in the query queue:
query_queue_timeout
is not changed, since that pending request received a cancel requestWhat I'm doing:
command start
, instead of the time when create slotCancellationException
Fixes #issue
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist: