You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "Bryan Beaudreault (Jira)" <ji...@apache.org> on 2022/07/05 18:03:00 UTC

[jira] [Resolved] (HBASE-27173) Consider adding ResourceLeakDetector to RefCnt

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

Bryan Beaudreault resolved HBASE-27173.
---------------------------------------
    Resolution: Duplicate

This ended up being added in HBASE-27170

> Consider adding ResourceLeakDetector to RefCnt
> ----------------------------------------------
>
>                 Key: HBASE-27173
>                 URL: https://issues.apache.org/jira/browse/HBASE-27173
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Bryan Beaudreault
>            Priority: Minor
>
> In my quest to figure out HBASE-27170, I ended up adding ResourceLeakDetector to RefCnt in my local fork. This immediately reports the leak to the logs, making it hard to miss. ResourceLeakDetector is already active in the netty layer, and the default state is designed to be very low overhead. We could add it directly to RefCnt, or make it further configurable if we're concerned about performance. Either way it's good to have and document, to aid future leak investigations.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)