[
https://issues.apache.org/jira/browse/HBASE-21628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16742796#comment-16742796
]
cong.han commented on HBASE-21628:
----------------------------------
[~stack]
add prefetch condition to scan is unnecessary, I will delete this part in next
patch.
the modify of this patch is a little complicated, I write a document to explain
the next questions.
I should write a document first and discuss if this modify is worth it, sorry.
> memory leak risk when ClientAsyncPrefetchScanner not close
> ----------------------------------------------------------
>
> Key: HBASE-21628
> URL: https://issues.apache.org/jira/browse/HBASE-21628
> Project: HBase
> Issue Type: Bug
> Reporter: cong.han
> Assignee: cong.han
> Priority: Major
> Attachments: HBASE-21328-v1.patch, HBASE-21628-v2.patch,
> HBASE-21628-v3.patch, HBASE-21628-v4.patch, HBASE-21628-v5.patch,
> HBASE-21628-v5.patch, HBASE-21628-v5.patch
>
>
> When we use ClientAsyncPrefetchScanner and we do two things below
> 1 Forgot to call close() method
> 2 The result are not full fetched
> The prefetch thread will not exit and leave a memory leak risk.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
