-
Notifications
You must be signed in to change notification settings - Fork 409
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
Fix potential data race in DynamicThreadPool #4648
Conversation
Signed-off-by: fuzhe1989 <[email protected]>
[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 submitting an approval review. |
/check-issue-triage-complete |
/run-sanitizer-test tsan |
/run-all-tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
/merge |
@fuzhe1989: It seems you want to merge this PR, I will help you trigger all the tests: /run-all-tests You only need to trigger If you have any questions about the PR merge process, please refer to pr process. 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. |
This pull request has been accepted and is ready to merge. Commit hash: 6604173
|
Coverage for changed files
Coverage summary
full coverage report (for internal network access only) |
Coverage for changed files
Coverage summary
full coverage report (for internal network access only) |
/run-sanitizer-test tsan |
Signed-off-by: fuzhe1989 [email protected]
What problem does this PR solve?
Issue Number: close #4595
Problem Summary:
DynamicThreadPool
relies on a counter to detect if all dynamic threads end, until when it can safely destruct.Previously the last instruction of
DynamicThreadPool::dynamicWork
is exactly the counter's decrement. This is an implicit contract.However after #4169 for recording thread-related metrics,
UPDATE_CUR_AND_MAX_METRIC
was added. It contains aSCOPE_EXIT
which will run after the counter's decrement and break the implicit contract.This introduces a risk that the main thread may find the counter is 0 and exit (and destruct all static variables like
TiFlashMetric
), however the dynamic threads do not really exit and try to visitTiFlashMetric
.What is changed and how it works?
Wrap the body of
DynamicThreadPool::dynamicWork
into a code block to ensure the decrement of counter is the last instruction.Check List
Tests
Side effects
Documentation
Release note