Limit the max connection number automatically
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 73
- Forks
- 41
- Avg merge
- 21h 3m
- Merged PRs (30d)
- 21
Description
Development Task
Each connection consumes some memory (maximum at 4 * conn-buffer-size). When there are too many connections, TiProxy may be OOM. TiProxy should reject new connections when its memory is almost used up.
Besides, TiProxy should also consider other resources, such as CPU and file descriptors.
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
The issue names no files, tests, or entry points. Start by locating where TiProxy accepts connections and where memory, CPU, and file-descriptor usage can be observed; then determine how resource limits should reject new connections. Done means connection admission accounts for the stated resources and prevents out-of-memory conditions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100