[jira] [Updated] (HBASE-10792) RingBufferTruck does not release its payload
[
https://issues.apache.org/jira/browse/HBASE-10792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated HBASE-10792:
-
Affects Version/s: hbase-10070
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] [Updated] (HBASE-10792) RingBufferTruck does not release its payload
[
https://issues.apache.org/jira/browse/HBASE-10792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated HBASE-10792:
-
Fix Version/s: hbase-10070
Cherry-picked using
{noformat}
$ svn merge -c 1579475 https://svn.apache.org/repos/asf/hbase/trunk
{noformat}
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, hbase-10070
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] [Updated] (HBASE-10792) RingBufferTruck does not release its payload
[
https://issues.apache.org/jira/browse/HBASE-10792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated HBASE-10792:
-
Status: Patch Available (was: Open)
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] [Updated] (HBASE-10792) RingBufferTruck does not release its payload
[
https://issues.apache.org/jira/browse/HBASE-10792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated HBASE-10792:
-
Attachment: HBASE-10792.00.patch
Here's a patch that changes RBT a little. Payload content can now be inspected
and references are removed at unload time. I don't know how this impacts
failure cases, I need to read up on the disruptor a bit more.
(cc [~fenghh], [~stack])
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] [Updated] (HBASE-10792) RingBufferTruck does not release its payload
[
https://issues.apache.org/jira/browse/HBASE-10792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-10792:
--
Attachment: HBASE-10792.00.patch
Retry
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] [Updated] (HBASE-10792) RingBufferTruck does not release its payload
[
https://issues.apache.org/jira/browse/HBASE-10792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated HBASE-10792:
-
Resolution: Fixed
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Committed to trunk. Thanks for the reviews.
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] [Updated] (HBASE-10792) RingBufferTruck does not release its payload
[
https://issues.apache.org/jira/browse/HBASE-10792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated HBASE-10792:
-
Fix Version/s: 0.99.0
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)
