leader drop when execute upgrade twice
Open
Nobody has claimed this yet.
status/discuss
- Dominant language
- Go
- Stars
- 466
- Forks
- 338
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 8
Description
First time. I execute
tiup cluster upgrade ga nightly, it timeout
But I need to upgrade, So I force upgrade
tiup cluster upgrade ga nightly --force
It success!!!
But. the leader on one server is zero
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
Reproduce the two tiup cluster upgrade ga nightly commands, first without --force and then with it, and inspect the resulting cluster state shown in the report. Trace the upgrade handling and identify why a server's leader count becomes zero after the forced retry. Done means the repeated upgrade no longer leaves that leader state inconsistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100