[ https://issues.apache.org/jira/browse/HBASE-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell resolved HBASE-2141. ----------------------------------- Resolution: Later Not wanted badly enough I'd say > Flexible thread pool for RPC server > ----------------------------------- > > Key: HBASE-2141 > URL: https://issues.apache.org/jira/browse/HBASE-2141 > Project: HBase > Issue Type: Improvement > Components: IPC/RPC > Reporter: Andrew Purtell > > 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. -- This message was sent by Atlassian JIRA (v6.2#6252)