TiFlash support capacity parameter to control store capacity like tikv
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1k
- Forks
- 423
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 24
Description
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
When deploy tidb cluster using tidb-operator, the operator use storage limit(limits.storage) as capacity parameter of tikv to control the tikv store capacity. While The tiflash doesn't have such the parameter to control store capacity, Maybe it better to support this like tikv and it is useful in k8s env.
2. What did you expect to see? (Required)
3. What did you see instead (Required)
4. What is your TiFlash version? (Required)
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 tracing how TiFlash currently determines store capacity and compare it with the TiKV capacity parameter used by TiDB Operator from limits.storage. No source files or tests are identified in the issue, so locate the relevant configuration and deployment paths first. Done means TiFlash accepts an equivalent capacity setting for Kubernetes deployments and has coverage verifying its effect.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, kubernetes
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100