Running ctl on all cluster instances with given role
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:
Currently it's hard to dynamically modify the configuration of a cluster through xx-ctl.
Describe the feature you'd like:
A separate ctl subcommand for cluster component, user can run ctl on any role with tiup cluster ctl $role [ARGS]
Describe alternatives you've considered:
These feature requires that ctl ARGS from user can't contain redundant attempt to designate endpoint, which seems quite hacky. An alternative would be providing a stronger shell execution environment that carries $endpoint and $tidb_ctl into tiup cluster exec.
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 with the tiup cluster ctl $role [ARGS] entry point and compare it with tiup cluster exec, focusing on how role instances and command arguments are selected. Done means users can run ctl arguments across every cluster instance with the given role without redundantly specifying an endpoint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100