[
https://issues.apache.org/jira/browse/HBASE-9333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13780022#comment-13780022
]
Hadoop QA commented on HBASE-9333:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12604819/9333.v1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified tests.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/7402//console
This message is automatically generated.
> 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 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
