hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abhishek Singh Chouhan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12747) IntegrationTestMTTR will OOME if launched with mvn verify
Date Tue, 20 Jan 2015 13:42:35 GMT

    [ https://issues.apache.org/jira/browse/HBASE-12747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14283818#comment-14283818
] 

Abhishek Singh Chouhan commented on HBASE-12747:
------------------------------------------------

Tested this out.I was still seeing OOME with heap bumped up to 2500m. 3000m seems to do the
trick and i saw no errors across several runs.I can submit a patch if we want to bump up Xmx
to 3000m [~apurtell]

> IntegrationTestMTTR will OOME if launched with mvn verify
> ---------------------------------------------------------
>
>                 Key: HBASE-12747
>                 URL: https://issues.apache.org/jira/browse/HBASE-12747
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.98.9
>            Reporter: Andrew Purtell
>            Priority: Minor
>         Attachments: org.apache.hadoop.hbase.mttr.IntegrationTestMTTR-output.txt.gz
>
>
> IntegrationTestMTRR will OOME if launched like:
> {noformat}
> cd hbase-it
> mvn verify -Dit.test=IntegrationTestMTTR
> {noformat}
> Linux environment, 7u67.
> Looks like we should bump the heap on the failsafe argline in the POM. 
> {noformat}
> 2014-12-22 11:24:07,725 ERROR [B.DefaultRpcServer.handler=2,queue=0,port=55672] ipc.RpcServer(2067):
Unexpected throwable o
> bject 
> java.lang.OutOfMemoryError: Java heap space
>         at org.apache.hadoop.hbase.regionserver.MemStoreLAB$Chunk.init(MemStoreLAB.java:246)
>         at org.apache.hadoop.hbase.regionserver.MemStoreLAB.getOrMakeChunk(MemStoreLAB.java:196)
>         at org.apache.hadoop.hbase.regionserver.MemStoreLAB.allocateBytes(MemStoreLAB.java:114)
>         at org.apache.hadoop.hbase.regionserver.MemStore.maybeCloneWithAllocator(MemStore.java:274)
>         at org.apache.hadoop.hbase.regionserver.MemStore.add(MemStore.java:229)
>         at org.apache.hadoop.hbase.regionserver.HStore.add(HStore.java:576)
>         at org.apache.hadoop.hbase.regionserver.HRegion.applyFamilyMapToMemstore(HRegion.java:3084)
>         at org.apache.hadoop.hbase.regionserver.HRegion.doMiniBatchMutation(HRegion.java:2517)
>         at org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:2284)
>         at org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:2239)
>         at org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:2243)
>         at org.apache.hadoop.hbase.regionserver.HRegionServer.doBatchOp(HRegionServer.java:4482)
>         at org.apache.hadoop.hbase.regionserver.HRegionServer.doNonAtomicRegionMutation(HRegionServer.java:3665)
>         at org.apache.hadoop.hbase.regionserver.HRegionServer.multi(HRegionServer.java:3554)
> {noformat}
> Another minor issue: After taking the OOME, the test executor will linger indefinitely
as a zombie. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message