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] [Commented] (HBASE-14827) Potential memory leak on REST server if state-full scanner is not deleted
Date Wed, 18 Nov 2015 02:20:10 GMT

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

Andrew Purtell commented on HBASE-14827:
----------------------------------------

bq. One open question is given stateless scanners, should statefull scanners be deprecated
and removed or not? 

Stateful scanners are by definition not REST-ful. We should have deprecated them when stateless
scanners were added, in retrospect.

Adding leases in the meantime before removal is no less problematic than their existence in
the first place. 

> 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