pingcap / pingcap/tidb-operator
hand on scale in if pod start after store already tombstone
Open
Nobody has claimed this yet.
type/bug
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
If the pod start after the store already tombstone, if will hang on scale in since it will not add the store-id label.
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 pod-start-after-store-tombstone scenario described in the issue and trace the TiDB Operator path that adds the store-id label. Done means scale-in completes without hanging when the store is already tombstoned; no source files or tests are named, so locating the relevant controller and coverage is part of the work.
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
- 35/100