-
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
a query may hang forever when its plan has a ParallelApply under TopN #24930
Comments
|
I upgrade its severity to critical since we have to pick it into |
related: #12759 |
Looks like a PR has already be merged. |
Please edit this comment or add a new comment to complete the following informationNot a bug
Duplicate bug
BugNote: Make Sure that 'component', and 'severity' labels are added 1. Root Cause Analysis (RCA) (optional)2. Symptom (optional)3. All Trigger Conditions (optional)4. Workaround (optional)5. Affected versions6. Fixed versions |
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
2. What did you expect to see? (Required)
The query can return an empty result.
3. What did you see instead (Required)
The query hangs forever.
4. What is your TiDB version? (Required)
Master
5. Root cause analysis!
All executors in TiDB have an implicit assumption that they will not be called again after returning an empty result(represent that they have no more data).
In this case, the underlying
ParallelApply
is called again by theTopN
after returning an empty result.Here is the stack:
The text was updated successfully, but these errors were encountered: