[jira] [Updated] (HBASE-14433) Set down the client executor core thread count from 256 to number of processors

[ https://issues.apache.org/jira/browse/HBASE-14433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-14433: -- Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 2.0.0 Status: Resolved (was: Pat

[jira] [Updated] (HBASE-14433) Set down the client executor core thread count from 256 to number of processors

[ https://issues.apache.org/jira/browse/HBASE-14433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-14433: -- Attachment: 14433v3.txt Retry > Set down the client executor core thread count from 256 to number of > proces

[jira] [Updated] (HBASE-14433) Set down the client executor core thread count from 256 to number of processors

[ https://issues.apache.org/jira/browse/HBASE-14433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-14433: -- Attachment: 14433v3.txt > Set down the client executor core thread count from 256 to number of > processors >

[jira] [Updated] (HBASE-14433) Set down the client executor core thread count from 256 to number of processors

[ https://issues.apache.org/jira/browse/HBASE-14433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-14433: -- Attachment: 14433v3.txt Try now jenkins is back. > Set down the client executor core thread count from 256 to

[jira] [Updated] (HBASE-14433) Set down the client executor core thread count from 256 to number of processors

[ https://issues.apache.org/jira/browse/HBASE-14433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-14433: -- Attachment: 14433v3.txt > Set down the client executor core thread count from 256 to number of > processors >

[jira] [Updated] (HBASE-14433) Set down the client executor core thread count from 256 to number of processors

[ https://issues.apache.org/jira/browse/HBASE-14433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-14433: -- Attachment: 14433v3.txt > Set down the client executor core thread count from 256 to number of > processors >

[jira] [Updated] (HBASE-14433) Set down the client executor core thread count from 256 to number of processors

[ https://issues.apache.org/jira/browse/HBASE-14433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-14433: -- Attachment: 14433v3.txt On second thoughts, leave keepalive at 60 seconds. Just change core thread count. >

[jira] [Updated] (HBASE-14433) Set down the client executor core thread count from 256 to number of processors

[ https://issues.apache.org/jira/browse/HBASE-14433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-14433: -- Release Note: Change the client executor core thread count to be number of processors instead of 256: i.e. the

[jira] [Updated] (HBASE-14433) Set down the client executor core thread count from 256 to number of processors

[ https://issues.apache.org/jira/browse/HBASE-14433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-14433: -- Attachment: 14433v2.txt Down the core client executor thread count from being equal to the max to instead be n

[jira] [Updated] (HBASE-14433) Set down the client executor core thread count from 256 to number of processors

[ https://issues.apache.org/jira/browse/HBASE-14433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-14433: -- Attachment: 14433 (1).txt The test failures seem like common zombies ... org.apache.hadoop.hbase.master.proce

[jira] [Updated] (HBASE-14433) Set down the client executor core thread count from 256 to number of processors

[ https://issues.apache.org/jira/browse/HBASE-14433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-14433: -- Attachment: 14433.txt Change for hbase-server and hbase-client tests only. Make it so core is 4 threads (max i

[jira] [Updated] (HBASE-14433) Set down the client executor core thread count from 256 to number of processors

[ https://issues.apache.org/jira/browse/HBASE-14433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-14433: -- Assignee: stack Status: Patch Available (was: Open) > Set down the client executor core thread count fro

[jira] [Updated] (HBASE-14433) Set down the client executor core thread count from 256 to number of processors

[ https://issues.apache.org/jira/browse/HBASE-14433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-14433: -- Attachment: (was: 14361.v3.txt) > Set down the client executor core thread count from 256 to number of > p

[jira] [Updated] (HBASE-14433) Set down the client executor core thread count from 256 to number of processors

[ https://issues.apache.org/jira/browse/HBASE-14433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-14433: -- Attachment: 14361.v3.txt Turn down thread and keepalive for test runs. > Set down the client executor core thr

[jira] [Updated] (HBASE-14433) Set down the client executor core thread count from 256 to number of processors

[ https://issues.apache.org/jira/browse/HBASE-14433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-14433: -- Issue Type: Sub-task (was: Bug) Parent: HBASE-14420 > Set down the client executor core thread count f