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

Fix potential data race in DynamicThreadPool #4648

Merged
merged 1 commit into from
Apr 14, 2022

Conversation

fuzhe1989
Copy link
Contributor

@fuzhe1989 fuzhe1989 commented Apr 14, 2022

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 a SCOPE_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 visit TiFlashMetric.

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

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

Side effects

  • Performance regression: Consumes more CPU
  • 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

None

@ti-chi-bot
Copy link
Member

ti-chi-bot commented Apr 14, 2022

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • SeaRise
  • bestwoody

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-chi-bot added release-note-none Denotes a PR that doesn't merit a release note. do-not-merge/needs-triage-completed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Apr 14, 2022
@fuzhe1989
Copy link
Contributor Author

/check-issue-triage-complete

@fuzhe1989
Copy link
Contributor Author

/run-sanitizer-test tsan

@fuzhe1989
Copy link
Contributor Author

/run-all-tests

@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label Apr 14, 2022
Copy link
Contributor

@bestwoody bestwoody left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@ti-chi-bot ti-chi-bot added status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels Apr 14, 2022
@fuzhe1989
Copy link
Contributor Author

/merge

@ti-chi-bot
Copy link
Member

@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 /merge once, and 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.

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.

@ti-chi-bot
Copy link
Member

This pull request has been accepted and is ready to merge.

Commit hash: 6604173

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Apr 14, 2022
@sre-bot
Copy link
Collaborator

sre-bot commented Apr 14, 2022

Coverage for changed files

Filename                                                                                             Regions    Missed Regions     Cover   Functions  Missed Functions  Executed       Lines      Missed Lines     Cover    Branches   Missed Branches     Cover
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
/home/jenkins/agent/workspace/tiflash-build-common/tiflash/dbms/src/Common/DynamicThreadPool.cpp          79                 1    98.73%          10                 0   100.00%          98                 1    98.98%          24                 1    95.83%
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
TOTAL                                                                                                     79                 1    98.73%          10                 0   100.00%          98                 1    98.98%          24                 1    95.83%

Coverage summary

Functions  MissedFunctions  Executed  Lines   MissedLines  Cover
17024      9512             44.13%    191878  96457        49.73%

full coverage report (for internal network access only)

@ti-chi-bot ti-chi-bot merged commit e41c545 into pingcap:master Apr 14, 2022
@fuzhe1989 fuzhe1989 deleted the fuzhe/fix_tsan branch April 14, 2022 03:58
@sre-bot
Copy link
Collaborator

sre-bot commented Apr 14, 2022

Coverage for changed files

Filename                                                                                             Regions    Missed Regions     Cover   Functions  Missed Functions  Executed       Lines      Missed Lines     Cover    Branches   Missed Branches     Cover
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
/home/jenkins/agent/workspace/tiflash-build-common/tiflash/dbms/src/Common/DynamicThreadPool.cpp          79                 1    98.73%          10                 0   100.00%          98                 1    98.98%          24                 1    95.83%
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
TOTAL                                                                                                     79                 1    98.73%          10                 0   100.00%          98                 1    98.98%          24                 1    95.83%

Coverage summary

Functions  MissedFunctions  Executed  Lines   MissedLines  Cover
17024      9512             44.13%    191878  96459        49.73%

full coverage report (for internal network access only)

@Benjamin2037
Copy link

/run-sanitizer-test tsan

@JaySon-Huang JaySon-Huang mentioned this pull request Apr 28, 2024
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-note-none Denotes a PR that doesn't merit a release note. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[TSAN] Data race at Metric Familiy
6 participants