pingcap / pingcap/tiup

Only restart components that modify configuration

Open
#316 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type/enhancement
Dominant language
Go
Stars
466
Forks
338
Avg merge
3d 7h
Merged PRs (30d)
8

Description

from:戚铮、李坤
现象:没有修改配置,reload 不指定 role 或 node 时会,也重启整个集群
建议:自动识别修改了哪个组件的配置,如果没有修改就跳过

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by tracing the reload path for cluster-wide reloads, then determine how component configuration changes are detected. Done means unchanged components are not restarted, and a reload with no configuration changes skips restarting the cluster.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.