[
https://issues.apache.org/jira/browse/HBASE-13065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14331995#comment-14331995
]
stack commented on HBASE-13065:
-------------------------------
@zhangduo How you think we end up on 32 bit jvm? We don't do -d32 in args we
pass... I checked the config we pass. We select 'JDK 1.7 (latest)' though
there are a bunch of options. That 'latest' is 1.7.0.25 might indicate that
this box has lagged its update. I could just remove the 'H?' machines from the
list of options which is currently: (ubuntu||Hadoop) && !jenkins-cloud-4GB &&
!H11
I just changed it to (ubuntu||Hadoop) && !jenkins-cloud-4GB && !H11 && !H3 to
remove H3 though wonder where the 32-bit comes from. No response from my
insider just yet. Hopefully he'll come back with something soon.
Thanks for digging in here.
> Increasing -Xmx when running TestDistributedLogSplitting
> --------------------------------------------------------
>
> Key: HBASE-13065
> URL: https://issues.apache.org/jira/browse/HBASE-13065
> Project: HBase
> Issue Type: Bug
> Components: test
> Reporter: zhangduo
> Assignee: zhangduo
> Fix For: 2.0.0, 1.0.1, 1.1.0, 0.98.11
>
> Attachments: 13065-fix.txt
>
>
> Found this in PreCommit Build reports
> https://builds.apache.org/job/PreCommit-HBASE-Build/12885/artifact/hbase-server/target/surefire-reports/org.apache.hadoop.hbase.master.TestDistributedLogSplitting-output.txt
> {noformat}
> 2015-02-18 03:45:42,141 WARN [RS:4;asf901:41265] util.Sleeper(97): We slept
> 59018ms instead of 1000ms, this is likely due to a long garbage collecting
> pause and it's usually bad, see
> http://hbase.apache.org/book.html#trouble.rs.runtime.zkexpired
> 2015-02-18 03:45:26,750 WARN [JvmPauseMonitor]
> util.JvmPauseMonitor$Monitor(167): Detected pause in JVM or host machine (eg
> GC): pause of approximately 39767ms
> GC pool 'PS MarkSweep' had collection(s): count=65 time=47720ms
> {noformat}
> Maybe we should increase the max heap size since this test starts 6
> regionservers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
