-
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
executor: fix data race of parallel apply operator (#24257) #24345
executor: fix data race of parallel apply operator (#24257) #24345
Conversation
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
/run-all-tests |
@guo-shaoge you're already a collaborator in bot's repo. |
/lgtm |
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by writing |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: cc80524
|
@ti-srebot: Your PR was out of date, I have automatically updated it for you. At the same time I will also trigger all tests for you: /run-all-tests If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes. 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 ti-community-infra/tichi repository. |
cherry-pick #24257 to release-5.0
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/24345
After apply modifications, you can push your change to this PR via:
What problem does this PR solve?
Issue Number: close #23280
Problem Summary:
TestApplyGoroutinePanic
test the situation of inner work panics. Sometime we got data race error. That's because:Feedback info will be read in step 3. But before step 4 really works, outer worker still runs normally, it will write Feedbackinfo.
So we got data race. (Only happens on feedback, it's disabled by default.)
What is changed and how it works?
What's Changed: In Apply's Close() method, we first notify outer worker to finish and wait untill it's really finished. Then we call outer exec's Close() method.
Related changes
pingcap/docs
/pingcap/docs-cn
:Check List
Tests: difficult to reproduce.
Side effects: no
Release note