[
https://issues.apache.org/jira/browse/HBASE-28401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17825419#comment-17825419
]
Hudson commented on HBASE-28401:
--------------------------------
Results for branch branch-3
[build #165 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/165/]:
(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/branch-3/165/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/165/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/165/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}
> Introduce a close method for memstore for release active segment
> ----------------------------------------------------------------
>
> Key: HBASE-28401
> URL: https://issues.apache.org/jira/browse/HBASE-28401
> Project: HBase
> Issue Type: Sub-task
> Components: in-memory-compaction, regionserver
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.6.0, 3.0.0-beta-2, 2.5.9
>
>
> Per the analysis in parent issue, we will always have an active segment in
> memstore even if it is empty, so if we do not call close on it, it will lead
> to a netty leak warning message.
> Although there is no real memory leak for this case, we'd better still fix it
> as it may hide other memory leak problem.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
