[jira] [Commented] (HBASE-10792) RingBufferTruck does not release its payload
[
https://issues.apache.org/jira/browse/HBASE-10792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941982#comment-13941982
]
Devaraj Das commented on HBASE-10792:
-
No objections, [~ndimiduk]
> 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, hbase-10070
>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)
[jira] [Commented] (HBASE-10792) RingBufferTruck does not release its payload
[
https://issues.apache.org/jira/browse/HBASE-10792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941922#comment-13941922
]
Nick Dimiduk commented on HBASE-10792:
--
[~enis], [~devaraj]: any objection to including this on hbase-10070 branch?
Local mode testing is basically broken without it.
> 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)
[jira] [Commented] (HBASE-10792) RingBufferTruck does not release its payload
[
https://issues.apache.org/jira/browse/HBASE-10792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941347#comment-13941347
]
Hudson commented on HBASE-10792:
FAILURE: Integrated in HBase-TRUNK #5025 (See
[https://builds.apache.org/job/HBase-TRUNK/5025/])
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)
[jira] [Commented] (HBASE-10792) RingBufferTruck does not release its payload
[
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)
[jira] [Commented] (HBASE-10792) RingBufferTruck does not release its payload
[
https://issues.apache.org/jira/browse/HBASE-10792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941162#comment-13941162
]
Hadoop QA commented on HBASE-10792:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12635650/HBASE-10792.00.patch
against trunk revision .
ATTACHMENT ID: 12635650
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop1.1{color}. The patch compiles against the hadoop
1.1 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/9048//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9048//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9048//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9048//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9048//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9048//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9048//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9048//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9048//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9048//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/9048//console
This message is automatically generated.
> 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
> 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)
[jira] [Commented] (HBASE-10792) RingBufferTruck does not release its payload
[
https://issues.apache.org/jira/browse/HBASE-10792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941051#comment-13941051
]
Himanshu Vashishtha commented on HBASE-10792:
-
+1
> 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
> 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)
[jira] [Commented] (HBASE-10792) RingBufferTruck does not release its payload
[
https://issues.apache.org/jira/browse/HBASE-10792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13940974#comment-13940974
]
Hadoop QA commented on HBASE-10792:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12635618/HBASE-10792.00.patch
against trunk revision .
ATTACHMENT ID: 12635618
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop1.1{color}. The patch compiles against the hadoop
1.1 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
{color:red}-1 core zombie tests{color}. There are 1 zombie test(s):
at
org.apache.hadoop.hbase.mapreduce.TestImportExport.testImport94Table(TestImportExport.java:230)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/9045//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9045//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9045//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9045//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9045//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9045//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9045//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9045//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9045//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9045//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/9045//console
This message is automatically generated.
> 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
> Attachments: 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)
[jira] [Commented] (HBASE-10792) RingBufferTruck does not release its payload
[
https://issues.apache.org/jira/browse/HBASE-10792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13940910#comment-13940910
]
stack commented on HBASE-10792:
---
+1
Its great. Thanks for keeping on w/ the strained metaphor!
> 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
> Attachments: 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)
