hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HBASE-14827) Potential memory leak on REST server if state-full scanner is not deleted
Date Wed, 18 Nov 2015 02:22:11 GMT

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

Andrew Purtell edited comment on HBASE-14827 at 11/18/15 2:21 AM:
------------------------------------------------------------------

bq. We should have deprecated them when stateless scanners were added, in retrospect.

See HBASE-14828 


was (Author: apurtell):
bq. We should have deprecated them when stateless scanners were added, in retrospect.

See HBASE-14828 for 

> Potential memory leak on REST server if state-full scanner is not deleted
> -------------------------------------------------------------------------
>
>                 Key: HBASE-14827
>                 URL: https://issues.apache.org/jira/browse/HBASE-14827
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Duo Xu
>
> Currently when people are using REST APIs to create state-full scanner, do scan with
scanner id and delete scanner. However, if the clients never call delete scanner or if the
clients are on cloud VMs and VMs get reboot before delete requests are sent, the resources
associated with the scanner will never be released on the REST server, "hbase.client.scanner.timeout.period"
will release the resources on region server side though.
> So this will cause memory leak on REST server in some cases.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message