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

test: fix data race in resouce control interceptor initialization #44789

Merged
merged 1 commit into from
Jun 19, 2023

Conversation

glorv
Copy link
Contributor

@glorv glorv commented Jun 19, 2023

What problem does this PR solve?

Issue Number: close #44776

Problem Summary:

What is changed and how it works?

The change move the ResourceControlInterceptor from main into domain to avoid data race. In the previous implementation, SetResourceControlInterceptor is run after dom is inited, so it's possible that session variable(tidb_enable_resource_control) initialization runs at the same time with SetResourceControlInterceptor.

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

Please refer to Release Notes Language Style Guide to write a quality release note.

None

@ti-chi-bot ti-chi-bot bot added the release-note-none Denotes a PR that doesn't merit a release note. label Jun 19, 2023
@glorv glorv requested a review from nolouch June 19, 2023 08:45
@ti-chi-bot ti-chi-bot bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jun 19, 2023
@glorv glorv requested a review from Connor1996 June 19, 2023 08:47
@glorv
Copy link
Contributor Author

glorv commented Jun 19, 2023

/retest

@ti-chi-bot ti-chi-bot bot added needs-1-more-lgtm Indicates a PR needs 1 more LGTM. approved labels Jun 19, 2023
@ti-chi-bot ti-chi-bot bot added lgtm and removed needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Jun 19, 2023
@ti-chi-bot
Copy link

ti-chi-bot bot commented Jun 19, 2023

[LGTM Timeline notifier]

Timeline:

  • 2023-06-19 08:53:53.611147407 +0000 UTC m=+6599.012397857: ☑️ agreed by hawkingrei.
  • 2023-06-19 09:28:35.643707816 +0000 UTC m=+8681.044958250: ☑️ agreed by nolouch.

@ti-chi-bot
Copy link

ti-chi-bot bot commented Jun 19, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hawkingrei, nolouch

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

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created to branch release-7.2: #44798.

@glorv glorv deleted the fix-rg-race branch June 20, 2023 02:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved lgtm needs-cherry-pick-release-7.2 release-note-none Denotes a PR that doesn't merit a release note. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Data race happens when bootstrap
4 participants