Please help reduce use system memory when drainer startup
Open
Nobody has claimed this yet.
status/help-wanted
- Dominant language
- Go
- Stars
- 291
- Forks
- 131
- Avg merge
- 5m
- Merged PRs (30d)
- 2
Description
Feature Request
Is your feature request related to a problem? Please describe:
When drainer startup it will take much memory , if tidb have a lot of history ddl
Describe the feature you'd like:
Please reduce use system memory when drainer startup.
Describe alternatives you've considered:
- When drainer startup , why need use history ddl ?
- History ddl just some records in table , why it take so much memory?
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 reproducing drainer startup with a TiDB instance containing substantial history DDL, then trace how that history is loaded and retained in memory. The issue names no files, tests, or entry points; done should include a measurable reduction in startup memory use while preserving required history DDL behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100