connLimiter limits should harmonize with existing Resource Manager limits
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.9k
- Forks
- 1.3k
- Avg merge
- 13d 21h
- Merged PRs (30d)
- 1
Description
There are different ways to set resource manager limits from connection prefix limits. This is confusing, and we should consolidate to the struct based limit config. See #3431 for context.
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 issue #3431 and tracing how connection-prefix limits are converted into Resource Manager limits. Compare the existing connection limiter paths with the struct-based limit configuration, then confirm that the consolidated behavior covers the different ways limits are currently set. Done means the confusing alternate configuration paths are harmonized without changing the intended limits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100