executor: fix CTE may be blocked when query report error (#33085)

[ti-srebot]

cherry-pick #33085 to release-5.2
You can switch your code base to this Pull Request by using git-extras:

# In tidb repo:
git pr https://github.com/pingcap/tidb/pull/33187

After apply modifications, you can push your change to this PR via:

git push [email protected]:ti-srebot/tidb.git pr/33187:release-5.2-f12ad1e6ca71

---

Signed-off-by: guo-shaoge [email protected]

What problem does this PR solve?

Issue Number: close #31302

Problem Summary:

mysql> explain with recursive cte(iter, first, second, result) as 
                       (select 1, first, second, first+second from src union all
                        select iter+1, second, result, second+result from cte where iter < 80 )
                        select * from cte;
+-------------------------------------+
| id                                  |
+-------------------------------------+
| CTEFullScan_18                      |
| CTE_0                               |
| ├─Projection_11(Seed Part)          |
| │ └─TableReader_13                  |
| │   └─TableFullScan_12              |
| └─Projection_14(Recursive Part)     |
|   └─Selection_15                    |
|     └─CTETable_16                   |
+-------------------------------------+

Why blocked:

1. Projection_14 will return overflow error
2. ProjectionExec.Close() will be called, and it will wait for projectionInputFetcher to finish.
3. projectionInputFetcher is blocked because CTETable_16 is blocked in CTETable_16.Next() because CTETable_16 is waiting for e.iterInTbl.GetBegCh().
4. CTE_0 will reset iterInTbl.begCh when error occurs, so begCh is reset, but nobody close begCh anymore. So CTETable_16 is blocked on <- e.iterInTbl.GetBegCh()

Why needs begCh:

1. Some executors(like IndexLookUpJoin) start workers in Open() so it will call child.Next() in Open() phase.
2. But data in iterInTbl is not ready in Open() phase, so these executor will read empty chunk which is unexpected.
3. That's why we need begCh, it indicates when data is ready. When computeSeedPart() or each iteration in CTEExec is done, iterInTbl will be readable, we will close(begCh) and CTETableExec will continue to return correct chunk.

But it's too complicated and caused this block bug. So I decide to change code in IndexLookUpJoin and remove begCh.

What is changed and how it works?

For IndexLookUpJoin, IndexNestedLookUpHashJoin and IndexLookUpMergeJoin, start works in Next() instead of Open().

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Side effects

• Performance regression: There maybe performance loss because workers in executor start in the first call of Next().
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

executor: fix CTE is block when query report error

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has not been approved.

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[ti-chi-bot]

@ti-srebot: This cherry pick PR is for a release branch and has not yet been approved by release team.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick, it must first be approved by the collaborators.

AFTER it has been approved by collaborators, please ping the release team in a comment to request a cherry pick review.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[ti-srebot]

/run-all-tests

[ti-srebot]

@guo-shaoge you're already a collaborator in bot's repo.

[ti-chi-bot]

@ti-srebot: PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.