You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2013/08/26 20:41:52 UTC

[jira] [Commented] (HBASE-9333) hbase.hconnection.threads.max should not be configurable else you get RejectedExecutionException

    [ https://issues.apache.org/jira/browse/HBASE-9333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750382#comment-13750382 ] 

stack commented on HBASE-9333:
------------------------------

It should be possible to set an upper bound though?  Is the executor misconfigured such that it can't be capped at an upper limit?
                
> 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
>             Fix For: 0.98.0, 0.96.0
>
>
> 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