[
https://issues.apache.org/jira/browse/HBASE-14433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14744387#comment-14744387
]
stack commented on HBASE-14433:
-------------------------------
The zombie is TestReplicasClient It seems to have a particular knack for
spinning up hundreds of threads. Comes of its slow-me-down-cp. Running it w/
the patch, it seems much better behaved with as many client threads as needed
in stead of with hundreds of idles. I don't think this thread-count the reason
for going zombie... but makes it easier to debug if less going on.
There is also TestRestoreSnapshotFromClient that is spinning up loads of client
threads.
> 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
> Attachments: 14433.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)
