You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2015/11/03 01:52:27 UTC

[jira] [Updated] (HBASE-14746) Run less client threads in tests

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

stack updated HBASE-14746:
--------------------------
    Assignee: stack
      Status: Patch Available  (was: Open)

> Run less client threads in tests
> --------------------------------
>
>                 Key: HBASE-14746
>                 URL: https://issues.apache.org/jira/browse/HBASE-14746
>             Project: HBase
>          Issue Type: Sub-task
>          Components: test
>            Reporter: stack
>            Assignee: stack
>         Attachments: lessthreads.txt
>
>
> Looking at thread counts reported by the nice 'after:' log message, I see the likes of TestReplicationKillSlaveRS and all of its derivatives reporting hundreds of threads (shows as over 1000 in one run here).
> Running the test standalone, I see the above run up the threads to 700 (only!). Need to figure why the discrepancy.
> The attached patch makes some difference -- cutting down the client thread count -- but not enough. Let me look more.



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