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

Posted to issues@hbase.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2013/10/03 01:02:43 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=13784596#comment-13784596 ] 

Hudson commented on HBASE-9333:
-------------------------------

SUCCESS: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #773 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/773/])
HBASE-9333 hbase.hconnection.threads.max should not be configurable else you get RejectedExecutionException (eclark: rev 1528618)
* /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java


> 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: 9333.v1.patch, 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 was sent by Atlassian JIRA
(v6.1#6144)