When tiup upgrades the cluster, the --offline subcommand supports the automatic reload function to prevent the unstopped cluster from still using the original cluster to run
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:
V5.3.3 --> V6.1.1
date: 2023/02/20 11:38
tiup cluster upgrade tidb533 v6.1.1 --offline (tidb533 is not closed)
Describe the feature you'd like:
Automatically reload the cluster after executing upgrade --offline
Why the featue is needed:
If you do not stop the cluster upgrade --offline first, you may miss executing the reload cluster, resulting in the original cluster process still running
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 from the tiup cluster upgrade --offline command entry point and trace how the upgrade completes when the cluster is still running. Verify the existing cluster process is reloaded automatically after the upgrade, and add or update the relevant tests if the command's behavior is covered there.
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
- 42/100