hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zheng Hu (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-22463) Some paths in HFileScannerImpl did not consider block#release which will exhaust the ByteBuffAllocator
Date Thu, 30 May 2019 07:25:00 GMT

     [ https://issues.apache.org/jira/browse/HBASE-22463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Zheng Hu resolved HBASE-22463.
------------------------------
      Resolution: Fixed
    Hadoop Flags: Reviewed

> 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)

Mime
View raw message