[HDDS-10385] Memory leak for thread local usages in OMClientRequest

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 2.0.0
• Component/s: Ozone Manager
• Labels: pull-request-available
• Assignee: Sumit Agrawal
• Reporter: Sumit Agrawal
• Created: 15/Feb/24 09:23
• Updated: 27/Feb/24 17:33
• Resolved: 21/Feb/24 06:19

Description

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 

Issue Links

• links to: GitHub Pull Request #6233
• links to: GitHub Pull Request #6234