[
https://issues.apache.org/jira/browse/HBASE-13065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14331996#comment-14331996
]
zhangduo commented on HBASE-13065:
----------------------------------
[~stack] There is an explicit bit info if the jvm is 64 bit I think.
{noformat}
Java HotSpot(TM) *64-Bit* Server VM (build 24.55-b03, mixed mode)
{noformat}
Our java -version
{noformat}
Java HotSpot(TM) Server VM (build 23.25-b01, mixed mode)
{noformat}
I found this when debugging TestHeapSize. It only failed on jenkins, and the
heap size info in assertion message is much less than the heap size on my 64bit
machine so it must be a less pointer size.
> 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)
