You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2015/02/18 18:51:11 UTC

[jira] [Resolved] (HBASE-13065) Increasing -Xmx when running TestDistributedLogSplitting

     [ https://issues.apache.org/jira/browse/HBASE-13065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-13065.
---------------------------
       Resolution: Fixed
    Fix Version/s: 0.98.11
                   1.1.0
                   1.0.1
                   2.0.0
         Assignee: zhangduo
     Hadoop Flags: Reviewed

Lets do that too [~Apache9] I pushed a pom change setting mx to 2800 in 0.98+

Resolving. Lets open new issue if still failing.

Thanks for digging in here [~Apache9]


> 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
>
>
> 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)