tiup cluster patch fails
Open
Nobody has claimed this yet.
status/investigating
type/bug
- Dominant language
- Go
- Stars
- 466
- Forks
- 338
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 8
Description
Bug Report
Please answer these questions before submitting your issue. Thanks!
- What did you do?
$ tiup cluster patch cluster1 ./tikv-v4.0.8-linux-amd64.tar.gz -R tikv --overwrite
...
Restarting component tikv
failed counting leader on 172.16.5.33:47906 (status addr http://172.16.5.33:47907/metrics), executing GET request for URL "http://172.16.5.33:47907/metrics" failed: Get http://172.16.5.33:47907/metrics: dial tcp 172.16.5.33:47907: connect: connection refused
Error: failed to evict store leader 172.16.5.33: metric tikv_raftstore_region_count{type="leader"} not found
- What did you expect to see?
patch success
-
What did you see instead?
-
What version of TiUP are you using (
tiup --version)?
tiup --version
v1.2.5 tiup
Go Version: go1.13
Git Branch: release-1.2
GitHash: 5b9cf5d
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 cluster patch cluster1 ./tikv-v4.0.8-linux-amd64.tar.gz -R tikv --overwrite command with TiUP v1.2.5 and inspect the cluster patch flow around leader eviction and the TiKV metrics request. Done means the patch completes successfully without the connection-refused or missing tikv_raftstore_region_count errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100