[
https://issues.apache.org/jira/browse/HBASE-28398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17820386#comment-17820386
]
Hudson commented on HBASE-28398:
--------------------------------
Results for branch master
[build #1019 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1019/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1019/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- Something went wrong running this stage, please [check relevant console
output|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1019//console].
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1019/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Make sure we close all the scanners in TestHRegion
> --------------------------------------------------
>
> Key: HBASE-28398
> URL: https://issues.apache.org/jira/browse/HBASE-28398
> Project: HBase
> Issue Type: Improvement
> Components: test
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.6.0, 2.4.18, 2.5.8, 3.0.0-beta-2
>
>
> While trying to figure out the root cause for memory leak in HBASE-27941, we
> found that in TestHRegion, we do not always close the opened scanner, which
> messes up the memory leak log.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
