execution summary may error
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1k
- Forks
- 423
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 24
Description
[2021/09/11 08:44:23.553 +08:00] [ERROR] [select_result.go:299] ["invalid cop task execution summaries length"] [conn=1049623] [expected=26] [received=19]
[2021/09/11 08:44:23.592 +08:00] [ERROR] [select_result.go:299] ["invalid cop task execution summaries length"] [conn=1049623] [expected=26] [received=19]
[2021/09/11 08:44:23.596 +08:00] [ERROR] [select_result.go:299] ["invalid cop task execution summaries length"] [conn=1049623] [expected=26] [received=19]
[2021/09/11 08:44:23.599 +08:00] [ERROR] [select_result.go:299] ["invalid cop task execution summaries length"] [conn=1049623] [expected=26] [received=19]
[2021/09/11 08:44:23.604 +08:00] [ERROR] [select_result.go:299] ["invalid cop task execution summaries length"] [conn=1049623] [expected=26] [received=19]
[2021/09/11 08:44:23.608 +08:00] [ERROR] [select_result.go:299] ["invalid cop task execution summaries length"] [conn=1049623] [expected=26] [received=19]
[2021/09/11 08:44:23.609 +08:00] [ERROR] [select_result.go:299] ["invalid cop task execution summaries length"] [conn=1049623] [expected=26] [received=19]
in another user, the execution summary on tidb is also not right.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at select_result.go:299, where the invalid cop task execution summaries length error is reported, and compare the expected and received counts in the provided logs. Trace how execution summaries are produced and consumed between TiFlash and TiDB; done means the summary is correct and the length error no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100