pingcap / pingcap/tidb-operator
do not lost the error when checking tidb health
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
when upgrading tidb, it keep unhealth and can not know what happens (tidb-1 already running and ready)
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 at pkg/controller/tidb_control.go#L73 and inspect how the TiDB health check handles errors during an upgrade. Reproduce the reported case where tidb-1 is running and ready but the cluster remains unhealthy, then verify that the underlying health-check error is preserved and visible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100