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

tidb-server: make max-procs in config file take effect under cgroups #17706

Merged
merged 6 commits into from Jun 6, 2020

Conversation

bobotu
Copy link
Contributor

@bobotu bobotu commented Jun 5, 2020

What problem does this PR solve?

Problem Summary:
In case the user wants to change this value under cgroups, the maxprocs.Set will overwrite the user's settings in the config file.

What is changed and how it works?

Call runtime.GOMAXPROCS(int(cfg.Performance.MaxProcs)) after maxprocs.Set.

Related changes

  • PR to update pingcap/docs/pingcap/docs-cn:
  • PR to update pingcap/tidb-ansible:
  • Need to cherry-pick to the release branch

Release note

  • make max-procs in config file take effect under cgroups

@codecov
Copy link

codecov bot commented Jun 5, 2020

Codecov Report

Merging #17706 into master will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             master     #17706   +/-   ##
===========================================
  Coverage   79.4719%   79.4719%           
===========================================
  Files           524        524           
  Lines        141436     141436           
===========================================
  Hits         112402     112402           
  Misses        19963      19963           
  Partials       9071       9071           

tennix
tennix previously approved these changes Jun 5, 2020
Copy link
Member

@tennix tennix left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Member

@jackysp jackysp left a comment

Choose a reason for hiding this comment

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

LGTM

@jackysp
Copy link
Member

jackysp commented Jun 5, 2020

/merge

@sre-bot sre-bot added the status/can-merge Indicates a PR has been approved by a committer. label Jun 5, 2020
@sre-bot
Copy link
Contributor

sre-bot commented Jun 5, 2020

Your auto merge job has been accepted, waiting for:

  • 17555
  • 17622

@sre-bot
Copy link
Contributor

sre-bot commented Jun 5, 2020

/run-all-tests

@sre-bot
Copy link
Contributor

sre-bot commented Jun 5, 2020

@bobotu merge failed.

@lysu
Copy link
Collaborator

lysu commented Jun 5, 2020

/merge

@sre-bot
Copy link
Contributor

sre-bot commented Jun 5, 2020

/run-all-tests

@sre-bot
Copy link
Contributor

sre-bot commented Jun 5, 2020

@bobotu merge failed.

@bobotu
Copy link
Contributor Author

bobotu commented Jun 6, 2020

/merge

@sre-bot
Copy link
Contributor

sre-bot commented Jun 6, 2020

/run-all-tests

@sre-bot sre-bot merged commit 3325840 into pingcap:master Jun 6, 2020
@bobotu bobotu deleted the fix-max-procs branch June 6, 2020 04:52
@bobotu
Copy link
Contributor Author

bobotu commented Aug 10, 2020

/run-cherry-picker

@ti-srebot
Copy link
Contributor

cherry pick to release-4.0 in PR #19094

bobotu pushed a commit to ti-srebot/tidb that referenced this pull request Sep 2, 2020
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/can-merge Indicates a PR has been approved by a committer. type/enhancement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants