[jira] [Updated] (HBASE-14433) Set down the client executor core thread count from 256 in tests

["stack (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-14433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-14433:
--------------------------
    Release Note: Tests run with client executors that have core thread count of 4 and a keepalive of 3 seconds. They used to default to 256 core threads and 60 seconds  for keepalive.  (was: Change the client executor core thread count to be number of processors instead of 256: i.e. the equivalent of the maximum threads allowed on client. The config to set it back to 256 or any other value is "hbase.hconnection.threads.core".

Also set it so core is set to default 4 threads in client core in tests (and keepalive is downed from a minute to 3 seconds).)
         Summary: Set down the client executor core thread count from 256 in tests  (was: Set down the client executor core thread count from 256 to number of processors)

> Set down the client executor core thread count from 256 in tests
> ----------------------------------------------------------------
>
>                 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)