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/09/20 01:35:51 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=13772468#comment-13772468 ]
stack commented on HBASE-9333:
------------------------------
+1 if you make the 4, the 128, and the 200 configurations (don't have to be in hbase-default.xml)... and does [~jdcryans] +1 it or you two still fighting (smile)
> 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
> Fix For: 0.98.0, 0.96.0
>
> Attachments: HBASE-9333-0.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