pingcap / pingcap/tidb-operator
VolumeReplacement is broken for PD, TICDC and TIDB components (except for TIKV)
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 TiDB Operator are you using?
1.55
What did you do?
Replace the storage class of PD in TIDB Spec
**What did you expect to see?
Disk replacement of all PD nodes one by one.
What did you see instead?
PD volume replacement is stuck due to leader eviction. This is due to regression caused by https://github.com/pingcap/tidb-operator/pull/6069, where leader eviction is not scoped to the TIKV component.
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
Review PR #6069 and trace the VolumeReplacement and leader-eviction path for PD, TiCDC, and TiDB, comparing its scoping with TiKV. Confirm the behavior by replacing PD's storage class in the TiDB Spec; done means PD volumes are replaced one node at a time without leader-eviction blocking the process.
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
- Mostly clear
- Newbie friendliness
- 38/100