You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Michael Stack (Jira)" <ji...@apache.org> on 2020/03/27 19:37:00 UTC
[jira] [Created] (HBASE-24072) Nightlies reporting
OutOfMemoryError: unable to create new native thread
Michael Stack created HBASE-24072:
-------------------------------------
Summary: Nightlies reporting OutOfMemoryError: unable to create new native thread
Key: HBASE-24072
URL: https://issues.apache.org/jira/browse/HBASE-24072
Project: HBase
Issue Type: Bug
Components: test
Reporter: Michael Stack
Seeing this kind of thing in nightly...
{code}
java.lang.RuntimeException: java.lang.OutOfMemoryError: unable to create new native thread
at org.apache.hadoop.hbase.mapreduce.TestMultithreadedTableMapper.beforeClass(TestMultithreadedTableMapper.java:83)
Caused by: java.lang.OutOfMemoryError: unable to create new native thread
at org.apache.hadoop.hbase.mapreduce.TestMultithreadedTableMapper.beforeClass(TestMultithreadedTableMapper.java:83)
{code}
Chatting w/ Nick and Huaxiang, doing the math, we are likely oversubscribing our docker container. It is set to 20G (The hosts are 48G). Fork count is 0.5C on a 16 CPU machine which is 8 *2.8G our current forked jvm size. Add the maven 4G and we could be over the top.
Play w/ downing the fork size (in earlier study we didn't seem to need this much RAM when running a fat long test). Let me also take th ms off the mvn allocation to see if that helps.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)