hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14433) Set down the client executor core thread count from 256 to number of processors
Date Wed, 16 Sep 2015 15:53:46 GMT

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

stack commented on HBASE-14433:
-------------------------------

Ok. Reverting the patch I applied last night because discussion ongoing over in HBASE-10449.
I'm instead going to just set limits for tests only.

> 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)

Mime
View raw message