[ https://issues.apache.org/jira/browse/HBASE-14433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14791038#comment-14791038 ]
Hudson commented on HBASE-14433: -------------------------------- FAILURE: Integrated in HBase-TRUNK #6814 (See [https://builds.apache.org/job/HBase-TRUNK/6814/]) HBASE-14433 Set down the client executor core thread count from 256 in tests: REAPPLY AGAIN (WAS MISSING JIRA) (stack: rev bd26386dc7205c9b30b8488bc094bd380ec09adb) * hbase-server/src/test/resources/hbase-site.xml * hbase-client/src/test/resources/hbase-site.xml > 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, 1.2.0, 1.3.0 > > Attachments: 14433 (1).txt, 14433.txt, 14433v2.txt, 14433v3.txt, > 14433v3.txt, 14433v3.txt, 14433v3.txt, 14433v3.txt, 14433v3.txt, > 14433v4.reapply.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)