[
https://issues.apache.org/jira/browse/HBASE-24134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17078826#comment-17078826
]
Hudson commented on HBASE-24134:
--------------------------------
Results for branch branch-2
[build #2590 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2590/]:
(/) *{color:green}+1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2590/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2590/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2590/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2590/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> 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)
