Code of Conduct
Search before asking
Describe the feature
Currently, the client-side does not support choosing between PooledByteBufAllocator and UnpooledByteBufAllocator, which lacks flexibility. We should provide this option.
Motivation
The PooledByteBufAllocator may occupy the memory of the Executors for an extended period, making it unsuitable for some users' scenarios(e.g. users only have limited resources, executors with very small memory, maybe less than 1g). In such cases, users may want to switch to UnpooledByteBufAllocator.
Describe the solution
Add a client config: rss.client.netty.client.pooled.allocator.enabled to decide whether to enable PooledByteBufAllocator.
Additional context
No response
Are you willing to submit PR?
Code of Conduct
Search before asking
Describe the feature
Currently, the client-side does not support choosing between
PooledByteBufAllocatorandUnpooledByteBufAllocator, which lacks flexibility. We should provide this option.Motivation
The
PooledByteBufAllocatormay occupy the memory of the Executors for an extended period, making it unsuitable for some users' scenarios(e.g. users only have limited resources, executors with very small memory, maybe less than 1g). In such cases, users may want to switch toUnpooledByteBufAllocator.Describe the solution
Add a client config:
rss.client.netty.client.pooled.allocator.enabledto decide whether to enablePooledByteBufAllocator.Additional context
No response
Are you willing to submit PR?