[HBASE-2141] Flexible thread pool for RPC server

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Component/s: IPC/RPC
• Assignee: Unassigned
• Reporter: Andrew Kyle Purtell
• Created: 17/Jan/10 20:33
• Updated: 11/Jun/22 23:03
• Resolved: 11/Jun/22 23:02

Description

Having a bounded thread pool is important, so availability can degrade gracefully (more or less), as opposed to the whole regionserver becoming livelocked. But, we don't need for the pool to be preallocated as is done currently. How about changing the RPC server thread pool such that the user can specify a minimum and maximum number of handler threads? The pool would start with the minimum, allocate more up to the max to handle additional concurrency, then terminate unused threads after some time back down to the minimum. Then we can do things like set a maximum of 100 handlers or such without taking on the overhead of 100 threads until it is needed.

Issue Links

• is related to: HBASE-2182 rpc/ipc refactor; x-version compatibility, nio, async, enveloping, sane timeouts, etc.