[
https://issues.apache.org/jira/browse/HBASE-10792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941211#comment-13941211
]
Hudson commented on HBASE-10792:
--------------------------------
FAILURE: Integrated in HBase-TRUNK-on-Hadoop-1.1 #123 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-1.1/123/])
HBASE-10792 RingBufferTruck does not release its payload (ndimiduk: rev 1579475)
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/FSHLog.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/RingBufferTruck.java
> RingBufferTruck does not release its payload
> --------------------------------------------
>
> Key: HBASE-10792
> URL: https://issues.apache.org/jira/browse/HBASE-10792
> Project: HBase
> Issue Type: Bug
> Components: Performance, wal
> Affects Versions: 0.99.0
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Fix For: 0.99.0
>
> Attachments: HBASE-10792.00.patch, HBASE-10792.00.patch
>
>
> Run a write-heavy workload (PerfEval sequentialWrite) out of a trunk sandbox
> and watch as HBase eventually dies with an OOM: heap space. Examining the
> heap dump shows an extremely large retained size of KeyValue and
> RingBufferTrunk instances. By my eye, the default value of
> {{hbase.regionserver.wal.disruptor.event.count}} is too large for such a
> small default heap size, or the RBT instances need to release their payloads
> after consumers retrieve them.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
