[
https://issues.apache.org/jira/browse/HBASE-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13172383#comment-13172383
]
nkeywal commented on HBASE-5064:
--------------------------------
@stack: yes,it should be that there are two many threads
- jvm limitation that we should manage with -Xmx or -Xss => but then we should
reproduce it on our machine as well (asd far as I know no one does reproduce it
locally), and we already set it to -Xmx1900m
- a limitation on the total number of thread on the machine => but it's quite
strange
- the ulimit per process, but then running the tests on multiple processes
should not change the probability to have an issue
The patch v2+ changed HBase configuration, On TestAdmin, we need 40 less
threads, so the benefit is not high. And I saw no real impact.
There are some stuff to look at, as sysctl kernel.threads-max, i will check if
it is printed in the default script.
> use surefire tests parallelization
> ----------------------------------
>
> Key: HBASE-5064
> URL: https://issues.apache.org/jira/browse/HBASE-5064
> Project: HBase
> Issue Type: Improvement
> Components: test
> Affects Versions: 0.94.0
> Reporter: nkeywal
> Assignee: nkeywal
> Priority: Minor
> Attachments: 5064.patch, 5064.patch, 5064.v2.patch, 5064.v3.patch,
> 5064.v4.patch, 5064.v5.patch, 5064.v6.patch, 5064.v7.patch
>
>
> To be tried multiple times on hadoop-qa before committing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
