Online rolling upgrade TiFlash
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1k
- Forks
- 423
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 24
Description
Users want their queries not to be greatly affected (meet unexpected errors) when upgrading TiFlash nodes
- How to check all replicas are ready after users changed the replica number. Issue: #1436
- TiDB-operator should wait for a TiFlash node to be upgraded is ready for providing service before upgrading the next TiFlash node. Issue: https://github.com/pingcap/tidb-operator/issues/3786, fix PR: https://github.com/pingcap/tidb-operator/pull/3789
- #2525
- TiFlash should return "Region not found" for batch cop to let TiDB retry when TiFlash is terminating #1460
Contributor guide
No contributing guide indexed for this repository
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 remaining work is the unchecked batch-cop behavior linked to issue #1460; start by reading that issue and the stated TiFlash termination scenario. Done means a terminating TiFlash returns "Region not found" for batch cop so TiDB can retry, while the other checklist items remain covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100