[ 
https://issues.apache.org/jira/browse/HBASE-22463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16870935#comment-16870935
 ] 

Hudson commented on HBASE-22463:
--------------------------------

Results for branch master
        [build #1168 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1168/]: (x) 
*{color:red}-1 overall{color}*
----
details (if available):

(x) {color:red}-1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1168//General_Nightly_Build_Report/]




(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1168//JDK8_Nightly_Build_Report_(Hadoop2)/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1168//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


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

Reply via email to