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

tikv_util: handle cgroup path building error (#12485) #76

Draft
wants to merge 1 commit into
base: merge-raftstore-proxy-to-6.1
Choose a base branch
from

Conversation

CalvinNeo
Copy link
Member

close tikv#12479, ref tikv#12585

Handle cgroup path building error gracefully

Signed-off-by: tabokie [email protected]

Co-authored-by: Ti Chi Robot [email protected]

What problem does this PR solve?

Issue Number: close #xxx

Problem Summary:

What is changed and how it works?

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

close tikv#12479, ref tikv#12585

Handle cgroup path building error gracefully

Signed-off-by: tabokie <[email protected]>

Co-authored-by: Ti Chi Robot <[email protected]>
@CalvinNeo CalvinNeo changed the base branch from raftstore-proxy to merge-raftstore-proxy-to-6.1 June 1, 2022 04:09
@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

cpu_cores_quota cause TiKV Panic
3 participants