TiFlash queries kept timeout during TiUP applying patches,
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 466
- Forks
- 338
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 8
Description
Bug Report
- What did you do?
User applied a patch in a TiDB 5.01 cluster (including 27 TiFlash nodes)
, and during the patching process TiFlash queries were not available/keeping throwing timeout errors.
-
What did you expect to see?
-
What did you see instead?
Retry of queries should be executed normally during the patching.
Even if a query was interrupted when a single node was applying the patch but it should have a chance to be executed in an interval between applying patches of two nodes, but not kept being interrupted.
There's no way for users to adjust the interval of applying patch between two different nodes. -
What version of TiUP are you using (
tiup --version)?
1.3.7
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 TiUP 1.3.7 patch workflow on a cluster with multiple TiFlash nodes, focusing on query behavior while nodes are patched. Investigate how patching intervals and query retries are handled. Done means queries can retry successfully between node updates, without repeated timeout interruptions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100