[
https://issues.apache.org/jira/browse/HBASE-21628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16742807#comment-16742807
]
Hadoop QA commented on HBASE-21628:
-----------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 5s{color}
| {color:red} HBASE-21628 does not apply to master. Rebase required? Wrong
Branch? See https://yetus.apache.org/documentation/0.8.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-21628 |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/15581/console |
| Powered by | Apache Yetus 0.8.0 http://yetus.apache.org |
This message was automatically generated.
> 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: ClientAsyncPrefetchScanner improvement.pdf,
> 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)
