-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
cop task runtime information is wrong in the index join #19847
Labels
component/executor
severity/major
sig/execution
SIG execution
type/bug
The issue is confirmed as a bug.
Comments
crazycs520
changed the title
Wrun
cop task runtime information is wrong in the index join
Sep 7, 2020
/label sig/execution |
Integrity check: |
/info |
Please edit this comment to complete the following informationBug1. Root Cause Analysis (RCA)As the Issue description said, the inner worker maybe use multiple IndexReader_37 executor to fetch data, but finally, TiDB only records the last executor time cost. 2. Symptom
3. All Trigger Conditions
4. Workaround (optional)
5. Affected versions[v4.0.0:v4.0.6] 6. Fixed versionsv4.0.7 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
component/executor
severity/major
sig/execution
SIG execution
type/bug
The issue is confirmed as a bug.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
As you can see in the upper picture, The inner worker of
IndexJoin_17
spend2.89010439s
to fetch data, but the childIndexReader_37(Build)
only spend1.999111ms
, It must be something wrong.The reason is the inner worker maybe use multiple
IndexReader_37
executor to fetch data, but finally, TiDB only record the last executor time cost.2. What did you expect to see? (Required)
3. What did you see instead (Required)
4. What is your TiDB version? (Required)
master
The text was updated successfully, but these errors were encountered: