[
https://issues.apache.org/jira/browse/HBASE-22463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849294#comment-16849294
]
Zheng Hu commented on HBASE-22463:
----------------------------------
After run about 12 hours in my test cluster with patch.v4, the
usedBufferCount was quite stable now. please see
[allocation-after-running-12h-with-patch-v4.png|https://issues.apache.org/jira/secure/attachment/12969957/allocation-after-running-12h-with-patch-v4.png]
> Some paths in HFileScannerImpl did not consider block#release which will
> exhaust the ByteBuffAllocator
> --------------------------------------------------------------------------------------------------------
>
> Key: HBASE-22463
> URL: https://issues.apache.org/jira/browse/HBASE-22463
> Project: HBase
> Issue Type: Sub-task
> Reporter: Zheng Hu
> Assignee: Zheng Hu
> Priority: Major
> Attachments: HBASE-22463.HBASE-21879.v1.patch,
> HBASE-22463.HBASE-21879.v1.patch, HBASE-22463.HBASE-21879.v1.patch,
> HBASE-22463.HBASE-21879.v2.patch, HBASE-22463.HBASE-21879.v3.patch,
> HBASE-22463.HBASE-21879.v4.patch, allocation-after-applied-patch-v2.png,
> allocation-after-running-12h-with-patch-v4.png, use-share-type-memory.png
>
>
> When I debug the issue HBASE-22422, I observed that the
> ByteBuffAllocator#usedBufCount will was always increasing and all direct
> ByteBuffers would be exhausted, which lead to may heap allocation happen.
> The comment here [1] is also related to this problem.
> Check the code path, the HFileScannerImpl is the biggest suspect, so create
> issue to address this.
> 1.
> https://issues.apache.org/jira/browse/HBASE-22387?focusedCommentId=16838446&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16838446
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
