storage checkpoint should also respect storage.temp.capacity
Open
Nobody has claimed this yet.
type/enhancement
- Dominant language
- C++
- Stars
- 1k
- Forks
- 423
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 24
Description
Enhancement
https://github.com/pingcap/tiflash/pull/10035 add storage.temp.capacity to limit spilling files,
but storage checkpoint also use storage.temp.dir, which respect storage.temp.capacity for now.
Contributor guide
No contributing guide indexed for this repository
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 reading the linked pull request #10035 and tracing how storage checkpoint uses storage.temp.dir and storage.temp.capacity. Done means storage checkpoint spilling also respects the configured storage.temp.capacity limit, with any relevant validation covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100