Apache
/
hbase
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

HBASE-24072 Nightlies reporting OutOfMemoryError: unable to create new native thread 

Set the forkcount down from 0.5C to 0.25C.
This commit is contained in:
stack 2020-04-01 16:05:59 -07:00
parent 09141681f6
commit 97a47ed0ee
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
dev-support/docker/Dockerfile
View File

@ -178,7 +178,7 @@ RUN mkdir -p /usr/lib/jvm && \
# TODO (nd): is this really true? investigate and file a ticket.
ENV SPOTBUGS_HOME '/opt/spotbugs'
ENV MAVEN_HOME '/opt/maven'
ENV MAVEN_OPTS '-Xms4G -Xmx4G'
ENV MAVEN_OPTS '-Xmx4G'
CMD ["/bin/bash"]

6
pom.xml
View File

@ -1412,10 +1412,10 @@
<!-- Fork count varies w/ CPU count. Setting is conservative. Up this
value is you want to burn through tests faster (could make for more failures
if more contention around resources). There is a matching MAVEN_ARG
in our yetus personality where we set the maven -T command to 0.5C too.
in our yetus personality where we set the maven -T command to 0.25C too.
-->
<surefire.firstPartForkCount>0.5C</surefire.firstPartForkCount>
<surefire.secondPartForkCount>0.5C</surefire.secondPartForkCount>
<surefire.firstPartForkCount>0.25C</surefire.firstPartForkCount>
<surefire.secondPartForkCount>0.25C</surefire.secondPartForkCount>
<surefire.firstPartGroups>org.apache.hadoop.hbase.testclassification.SmallTests</surefire.firstPartGroups>
<surefire.secondPartGroups>org.apache.hadoop.hbase.testclassification.MediumTests</surefire.secondPartGroups>
<surefire.testFailureIgnore>false</surefire.testFailureIgnore>