pingcap / pingcap/tidb-operator
TiDB Operator OOM
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
Bug Report
What version of Kubernetes are you using?
v1.15.3
What version of TiDB Operator are you using?
v1.1.2
What storage classes exist in the Kubernetes cluster and what are used for PD/TiKV pods?
What's the status of the TiDB cluster pods?
What did you do?
What did you expect to see?
TiDB Operator works normally without OOM killed
What did you see instead?
TiDB Operator takes several GB memory and eventually gets OOM killed
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
Start by reproducing the report with Kubernetes v1.15.3 and TiDB Operator v1.1.2. Use the issue's kubectl commands to inspect the controller-manager pod, cluster pods, storage classes, and PVCs, then identify what causes memory growth. Done means explaining or fixing the multi-GB memory use and verifying that the operator no longer gets OOM-killed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100