Support concurrence during `tiup cluster patch`
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 466
- Forks
- 338
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 8
Description
Feature Request
Is your feature request related to a problem? Please describe:
when we use tiup cluster patch patch more than one node, now tiup patch one by one, but we can do it concurrently.
Describe the feature you'd like:
tiup cluster patch patch concurrently.
Why the featue is needed:
improve patch speed
Describe alternatives you've considered:
Teachability, Documentation, Adoption, Migration Strategy:
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 the tiup cluster patch command and trace how patches are currently applied to multiple nodes. Determine the concurrency behavior needed to improve patch speed, then verify that patching more than one node completes concurrently without breaking cluster operations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100