[
https://issues.apache.org/jira/browse/HBASE-24134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17077548#comment-17077548
]
Michael Stack commented on HBASE-24134:
---------------------------------------
Full test suite on jdk11 passes with heaps of 2200m
{code}
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 51:32 min (Wall Clock)
[INFO] Finished at: 2020-04-07T20:22:57+00:00
[INFO] Final Memory: 134M/9010M
[INFO] ------------------------------------------------------------------------
{code}
Let me put up a patch
> Down forked JVM heap size from 2800m to 2200m for jdk8 and jdk11
> ----------------------------------------------------------------
>
> Key: HBASE-24134
> URL: https://issues.apache.org/jira/browse/HBASE-24134
> Project: HBase
> Issue Type: Sub-task
> Reporter: Michael Stack
> Priority: Major
>
> Docker container we run tests in is hardcoded 20G. Our fork count is 0.25C
> currently. The jenkins machines are 16CPUs. 0.25C means 4CPUs so 4 forks
> running at any one time. Our current forked JVM heap size is 2800m if jdk8 or
> 3200m if jdk11. If we want to move our fork count to 0.5C, then that means 8
> forks possibly running at once: i.e. 8 * 2800 = 22.4G... i.e. too big for the
> container. This issue is about running w/ smaller forked jvm heap size. If
> 2200m then, its 19.6G which is cutting it close but might allow us sqeeze
> through (mvn takes 4G!). Lets see.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
