[
https://issues.apache.org/jira/browse/HBASE-9333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13773859#comment-13773859
]
stack commented on HBASE-9333:
------------------------------
[~liochon] Rather than reject, should we block? Fine on caping by
regionservers. Is that accessible in the AsyncProcess context? What number of
threads total would we be talking about?
> hbase.hconnection.threads.max should not be configurable else you get
> RejectedExecutionException
> ------------------------------------------------------------------------------------------------
>
> Key: HBASE-9333
> URL: https://issues.apache.org/jira/browse/HBASE-9333
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.95.2
> Reporter: Jean-Daniel Cryans
> Assignee: Elliott Clark
> Priority: Critical
> Fix For: 0.98.0, 0.96.0
>
> Attachments: HBASE-9333-0.patch, HBASE-9333-1.patch,
> HBASE-9333-2.patch
>
>
> Trying to set hbase.hconnection.threads.max to a lower number than its
> default of Integer.MAX_VALUE simply results in a RejectedExecutionException
> when the max is reached. It seems there's no good reason to keep this
> configurable.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
