pingcap / pingcap/community

Incubating Program: Dynamic Configuration Change

Open
#89 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

incubating-request/feature status/LGT1
Dominant language
No language data
Stars
267
Forks
154
PR merge metrics
No merged PRs in 30d

Description

Incubating Program

Dynamic Configuration Change

Describe the feature or project you want to incubate:
Summary

This proposal proposes a unified way to manage the configuration options of TiDB, TiKV, and PD by storing them in PD and support dynamically change the configuration options by using the same way among the different components which can greatly improve usability.

Motivation

Here are some reasons why we need to do it:

  • For now, each component in TiDB cluster has its own configuration file, which is hard for management. we need a unified way to manage the configuration options of all components
  • Although some configuration options support dynamic modification, the operations need to learn a lot to use them properly since we have multiple entries, e.g., pd-ctl, tikv-ctl, and SQL, resulting in poor usability. For better usability, provide a unified way to modify them dynamically.
Your RFC/Proposal?

https://github.com/pingcap/tidb/pull/13660

Contributor guide

No contributing guide indexed for this repository

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

Start with the RFC/proposal in pull request 13660 and review how configuration is currently managed across TiDB, TiKV, and PD. The proposal's intended outcome is a unified configuration store in PD with a consistent way to change supported options dynamically across components.

Written by the indexing model from the issue text.

Assessment

Tech stack
sql
Domain
databases, distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.