Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 16 Sep 2015 07:55:46 +0000 (UTC)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12864015.1442262264000.352336.1442390146288@Atlassian.JIRA>
In-Reply-To: <JIRA.12864015.1442262264000@Atlassian.JIRA>
References: <JIRA.12864015.1442262264000@Atlassian.JIRA>
 <JIRA.12864015.1442262264914@arcas>
Subject: [jira] [Commented] (HBASE-14433) Set down the client executor core
 thread count from 256 to number of processors
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hadoop QA commented on HBASE-14433:
-----------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12756161/14433v3.txt
  against master branch at commit fe2c4f630d3b5f3346c9ee9f95c256186c9e6907.
  ATTACHMENT ID: 12756161

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 6 new or modified tests.

    {color:green}+1 hadoop versions{color}. The patch compiles with all supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0 2.7.1)

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 protoc{color}.  The applied patch does not increase the total number of protoc compiler warnings.

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any warning messages.

    {color:green}+1 checkstyle{color}.  The applied patch does not increase the total number of checkstyle errors

    {color:green}+1 findbugs{color}.  The patch does not introduce any  new Findbugs (version 2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 lineLengths{color}.  The patch does not introduce lines longer than 100

  {color:green}+1 site{color}.  The mvn post-site goal succeeds with this patch.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/15613//testReport/
Release Findbugs (version 2.0.3) 	warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/15613//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors: https://builds.apache.org/job/PreCommit-HBASE-Build/15613//artifact/patchprocess/checkstyle-aggregate.html

  Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/15613//console

This message is automatically generated.

> Set down the client executor core thread count from 256 to number of processors
> -------------------------------------------------------------------------------
>
>                 Key: HBASE-14433
>                 URL: https://issues.apache.org/jira/browse/HBASE-14433
>             Project: HBase
>          Issue Type: Sub-task
>          Components: test
>            Reporter: stack
>            Assignee: stack
>             Fix For: 2.0.0
>
>         Attachments: 14433 (1).txt, 14433.txt, 14433v2.txt, 14433v3.txt, 14433v3.txt, 14433v3.txt, 14433v3.txt, 14433v3.txt, 14433v3.txt
>
>
> HBASE-10449 upped our core count from 0 to 256 (max is 256). Looking in a recent test run core dump, I see up to 256 threads per client and all are idle. At a minimum it makes it hard reading test thread dumps. Trying to learn more about why we went a core of 256 over in HBASE-10449. Meantime will try setting down configs for test.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)