pingcap / pingcap/tidb-operator
Update the way to set tikv_gc_life_time
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
Feature Request
Is your feature request related to a problem? Please describe:
https://github.com/pingcap/tidb/pull/21988 updates the way to set tikv_gc_life_time, after that we can set it via sysvars instead of updating mysql.tidb directly.
Describe the feature you'd like:
Describe alternatives you've considered:
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 by reviewing pingcap/tidb PR 21988 and the TiDB Operator code that handles tikv_gc_life_time. Determine where the operator currently updates mysql.tidb and identify the relevant tests or configuration entry points; done means the setting uses sysvars instead and the behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100