[ https://issues.apache.org/jira/browse/HBASE-28133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17774336#comment-17774336 ]
Hudson commented on HBASE-28133: -------------------------------- Results for branch branch-2 [build #902 on builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/902/]: (x) *{color:red}-1 overall{color}* ---- details (if available): (/) {color:green}+1 general checks{color} -- For more information [see general report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/902/General_20Nightly_20Build_20Report/] (/) {color:green}+1 jdk8 hadoop2 checks{color} -- For more information [see jdk8 (hadoop2) report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/902/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/] (x) {color:red}-1 jdk8 hadoop3 checks{color} -- For more information [see jdk8 (hadoop3) report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/902/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/] (/) {color:green}+1 jdk11 hadoop3 checks{color} -- For more information [see jdk11 report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/902/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} > TestSyncTimeRangeTracker fails with OOM with small -Xms values > -------------------------------------------------------------- > > Key: HBASE-28133 > URL: https://issues.apache.org/jira/browse/HBASE-28133 > Project: HBase > Issue Type: Bug > Affects Versions: 2.4.17 > Reporter: Istvan Toth > Assignee: Istvan Toth > Priority: Major > Labels: Arm64, test > Fix For: 2.6.0, 2.4.18, 2.5.6, 3.0.0-beta-1 > > > Edit2: It's not the OS, it's the -Xms value determined from the host memory > size. > Edit: It's related to the OS and it's default java 8 , not to the processor > architecture. > This test seems to be cutting real close to the heap size. > On ARM, it consistently fails on my RHEL8.8 Aarch64 VM with Java 8. > {noformat} > mvn test -P runDevTests -Dtest.build.data.basedirectory=/ram2G > -Dhadoop.profile=3.0 -fn -B -Dtest=TestSyncTimeRangeTracker* -pl hbase-server > ... > [ERROR] > org.apache.hadoop.hbase.regionserver.TestSyncTimeRangeTracker.testConcurrentIncludeTimestampCorrectness > Time elapsed: 1.969 s <<< ERROR! > java.lang.OutOfMemoryError: Java heap space > {noformat} > It seems that Java on ARM has some higher memory overhead than x86_64. > Simply bumping -Xmx from the default 2200m to 2300m allows it to pass. > {noformat} > mvn test -P runDevTests -Dtest.build.data.basedirectory=/ram2G > -Dhadoop.profile=3.0 -fn -B -Dtest=TestSyncTimeRangeTracker* -pl hbase-server > -Dsurefire.Xmx=2300m > ... > [INFO] Running org.apache.hadoop.hbase.regionserver.TestSyncTimeRangeTracker > [INFO] Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.395 > s - in org.apache.hadoop.hbase.regionserver.TestSyncTimeRangeTracker > {noformat} > However, the real solution should be reducing the memory usage for this test. > -- This message was sent by Atlassian Jira (v8.20.10#820010)