tiup cluster reload specifies the node/role, but all the configurations of the entire cluster are refreshed
Open
Nobody has claimed this yet.
type/feature-request
- 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 reload dba-test -R prometheus
-
What did you expect to see?
Only the prometheus configuration is refreshed -
What did you see instead?
The configuration of all nodes in the cluster is refreshed -
What version of TiUP are you using (
tiup --version)?
tiup v1.5.2
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 reload command entry point and reproduce tiup cluster reload dba-test -R prometheus with TiUP v1.5.2 or the current version. Trace how the node or role selector is handled; done means only the Prometheus configuration is refreshed, while other cluster configurations remain unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100