improve cluster and dm Intuitive
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 466
- Forks
- 338
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 8
Description
1、tiup cluster display 能够展示 tikv 的 label 信息，更直观【现有配置文件 yaml 文件，不直观】
2、tiup dm 能够展示 bound 的 source 信息，更直观 【用于直观看现有 worker bound 哪个上游 mysql】
需求场景：
1、tiup 管理 tidb 大集群，且 tikv 实例很多情况下，yaml 格式可读性差，肉眼无法核对，容易出现不合规 label，比如同台机器可能存在不一样的 label，进而导致异常场景下，集群服务异常
2、tiup 管理 dm 集群，现在 dm 集群 bound 信息未显示，不利于问题诊断，易用性不高
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 by locating the tiup cluster display and tiup dm bound-information entry points. The issue requests that cluster display include TiKV label information and that DM display include each bound source; done means both views expose these details clearly. No files or tests are named, so the relevant implementation and validation paths must first be identified.
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
- Needs clarification
- Newbie friendliness
- 35/100