Support change pd config after bootstraping
Open
Nobody has claimed this yet.
difficulty/hard
status/TODO
type/enhancement
type/feature-request
- Dominant language
- Go
- Stars
- 466
- Forks
- 338
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 8
Description
Feature Request
The pd server doesn't receive config changes from config file after bootstrapping, so it's of no use to change the config of pd in tiup cluster edit-config. To support it, we should call pd API to set the config every time pd config changed.
Releated question: https://asktug.com/t/topic/34397/
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 edit-config flow and trace how PD configuration changes are handled after bootstrapping. Use the PD API as the relevant integration point; done means config changes are sent to the running PD server whenever its configuration changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100