could brpc make IdTraits::MAX_ENTRIES/INIT_GC_SIZE a configurable option?
Open
- Dominant language
- C++
- Stars
- 17.6k
- Forks
- 4.1k
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 69
Description
I encountered the problem that brpc would report eagain error. After trying to change the MAX_ENTRIES of TidTraits from 65536 to 655360, the problem no longer occurred.
I noticed that MAX_ENTRIES and INIT_GC_SIZE of TidTraits are set to the same size. Does this mean that GC will never be triggered? Should MAX_ENTRIES or INIT_GC_SIZE be made configurable?
Contributor guide
Research direction
Locate the TidTraits definition and trace every use of MAX_ENTRIES and INIT_GC_SIZE, then inspect how the reported eagain condition relates to those limits and garbage collection. The work is complete when the relevant values can be configured as intended and the behavior is validated by appropriate project tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100