[
https://issues.apache.org/jira/browse/HBASE-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054544#comment-13054544
]
Jean-Daniel Cryans commented on HBASE-3852:
-------------------------------------------
I'm not sure it fixes the problem, since the issue here is about users not
getting back to close even tho there's still more data. We patched in something
at SU that we've been running for more than a month, but it is specific to our
usecase. Anyways, feel free to inspire yourself with those two commits:
https://github.com/stumbleupon/hbase/commit/7bcc63ee22f7e0218fb7225f387ffc0bd2279f59#src/main/java/org/apache/hadoop/hbase/thrift/ThriftServer.java
https://github.com/stumbleupon/hbase/commit/3d08cc8ad5abfec11ee0340d5a75a2b308854e17#src/main/java/org/apache/hadoop/hbase/thrift/ThriftServer.java
> ThriftServer leaks scanners
> ---------------------------
>
> Key: HBASE-3852
> URL: https://issues.apache.org/jira/browse/HBASE-3852
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.90.2
> Reporter: Jean-Daniel Cryans
> Assignee: Ted Yu
> Priority: Critical
> Fix For: 0.92.0
>
> Attachments: 3852.txt
>
>
> The scannerMap in ThriftServer relies on the user to clean it by closing the
> scanner. If that doesn't happen, the ResultScanner will stay in the thrift
> server's memory and if any pre-fetching was done, it will also start
> accumulating Results (with all their data).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
