pingcap / pingcap/tidb-operator
set gc.ratio-threshold to -1 when performing pitr restore
Open
Nobody has claimed this yet.
v2
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
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 pull/6267, which the issue identifies as the related implementation for PITR restore behavior. Trace the restore path and verify that gc.ratio-threshold is set to -1 during PITR restores; done means the setting is applied only for that restore flow and the relevant checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100