You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2024/03/11 10:23:00 UTC

[jira] [Resolved] (HBASE-28401) Introduce a close method for memstore for release active segment

     [ https://issues.apache.org/jira/browse/HBASE-28401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Duo Zhang resolved HBASE-28401.
-------------------------------
    Fix Version/s: 2.6.0
                   3.0.0-beta-2
                   2.5.9
     Hadoop Flags: Reviewed
       Resolution: Fixed

Pushed to branch-2.5+.

Thanks [~bbeaudreault] for reviewing!

> 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)