You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Janus Chow (Jira)" <ji...@apache.org> on 2024/02/15 09:29:00 UTC

[jira] [Commented] (HDDS-10385) Memory leak for thread local usages in OMClientRequest

    [ https://issues.apache.org/jira/browse/HDDS-10385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17817622#comment-17817622 ] 

Janus Chow commented on HDDS-10385:
-----------------------------------

[~sumitagrawl] Could you share more details on this?

We haven't monitored memory leak in our cluster yet.

> Memory leak for thread local usages in OMClientRequest
> ------------------------------------------------------
>
>                 Key: HDDS-10385
>                 URL: https://issues.apache.org/jira/browse/HDDS-10385
>             Project: Apache Ozone
>          Issue Type: Bug
>          Components: Ozone Manager
>            Reporter: Sumit Agrawal
>            Priority: Critical
>
> As part of *HDDS-8974. Introduce detailed lock information*
> Below omLockDetails is declared which is private to the instance and consume thread local resource of thread. But this resource is never released.
> private final ThreadLocal<OMLockDetails> omLockDetails =
> ThreadLocal.withInitial(OMLockDetails::new);
>  
> This will cause memory leak and thread local memory keeps increasing with each new Request object.
>  
> Need avoid usages of thread local as instance level; or need use as static or as singleton to reuse same resource.
>  
> cc: [~Symious] [~Sammi] 



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org