Skip to content
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

Closed
crazycs520 opened this issue Sep 7, 2020 · 4 comments · Fixed by #19849
Closed

cop task runtime information is wrong in the index join #19847

crazycs520 opened this issue Sep 7, 2020 · 4 comments · Fixed by #19849
Assignees
Labels
component/executor severity/major sig/execution SIG execution type/bug The issue is confirmed as a bug.

Comments

@crazycs520
Copy link
Contributor

crazycs520 commented Sep 7, 2020

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

image

As you can see in the upper picture, The inner worker of IndexJoin_17 spend 2.89010439s to fetch data, but the child IndexReader_37(Build) only spend 1.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

@crazycs520 crazycs520 added the type/bug The issue is confirmed as a bug. label Sep 7, 2020
@crazycs520 crazycs520 changed the title Wrun cop task runtime information is wrong in the index join Sep 7, 2020
@crazycs520 crazycs520 self-assigned this Sep 7, 2020
@wshwsh12
Copy link
Contributor

wshwsh12 commented Sep 8, 2020

/label sig/execution

@sre-bot
Copy link
Contributor

sre-bot commented Sep 14, 2020

Integrity check:
component RCA symptom affect_version fix_version fields are empty
@crazycs520

@pingcap pingcap deleted a comment from sre-bot Sep 14, 2020
@crazycs520
Copy link
Contributor Author

/info

@ti-srebot
Copy link
Contributor

ti-srebot commented Sep 14, 2020

Please edit this comment to complete the following information

Bug

1. 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

  • N/A

3. All Trigger Conditions

  • N/A

4. Workaround (optional)

  • N/A

5. Affected versions

[v4.0.0:v4.0.6]

6. Fixed versions

v4.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.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants