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

Hudson commented on HBASE-21007:
--------------------------------

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

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1079//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/branch-2/1079//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/branch-2/1079//JDK8_Nightly_Build_Report_(Hadoop3)/]


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


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


> Memory leak in HBase rest server
> --------------------------------
>
>                 Key: HBASE-21007
>                 URL: https://issues.apache.org/jira/browse/HBASE-21007
>             Project: HBase
>          Issue Type: Bug
>          Components: REST
>    Affects Versions: 1.4.0, 1.4.6
>            Reporter: Bosko Devetak
>            Assignee: Bosko Devetak
>            Priority: Critical
>             Fix For: 3.0.0, 1.5.0, 1.2.7, 1.3.3, 2.0.2, 2.2.0, 2.1.1, 1.4.7
>
>         Attachments: HBASE-21007.001.patch, HBASE-21007.002.patch
>
>
> When using the URIs like this:
>  
>           /sometable/*?limit=$limit&startrow=$startrow&endrow=$endrow
>  
> where *$limit* is smaller than the range between *$startrow* and *$endrow*, 
> the rest server will start leaking memory.
>  
>  
> The bug is in the *TableScanResource.java* class. Basically, the 
> ResultScanner is not being closed in next() method when the limit has been 
> reached.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to