[HBASE-22463] Some paths in HFileScannerImpl did not consider block#release which will exhaust the ByteBuffAllocator

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0-alpha-1, 2.3.0
• Hadoop Flags: Reviewed
• Assignee: Zheng Hu
• Reporter: Zheng Hu
• Created: 23/May/19 13:44
• Updated: 01/Jul/22 21:46
• Resolved: 30/May/19 07:24

Description

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

Issue Links

• relates to: HBASE-22480 Get block from BlockCache once and return this block to BlockCache twice make ref count error.
• links to: GitHub Pull Request #257