Cluster check the memory.max or memory.limit_in_bytes of cgroup
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 466
- Forks
- 338
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 8
Description
Feature Request
Is your feature request related to a problem? Please describe:
Customer deploy tidb failed and do not know why: https://internal.pingcap.net/jira/browse/ONCALL-4258
Describe the feature you'd like:
Check whether the memory.max or memory.limit_in_bytes of the cgroup configuration exceeds the range of int64.
Why the featue is needed:
Suggested by On-call team
Describe alternatives you've considered:
Teachability, Documentation, Adoption, Migration Strategy:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, entry points, or tests. Start by locating the Go code that reads cgroup memory.max or memory.limit_in_bytes, then inspect how those values are parsed and validated. Done means the cluster check detects values outside the int64 range and has coverage for the relevant cgroup configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, linux
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100