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

[jira] [Resolved] (HDDS-11201) worker queue of FullTableCache cleanup consume much memory

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

Sadanand Shenoy resolved HDDS-11201.
------------------------------------
    Fix Version/s: 1.5.0
       Resolution: Fixed

> worker queue of FullTableCache cleanup consume much memory
> ----------------------------------------------------------
>
>                 Key: HDDS-11201
>                 URL: https://issues.apache.org/jira/browse/HDDS-11201
>             Project: Apache Ozone
>          Issue Type: Bug
>          Components: Ozone Manager
>            Reporter: Sumit Agrawal
>            Assignee: Sumit Agrawal
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.5.0
>
>         Attachments: image-2024-07-18-11-17-20-894.png
>
>
> As observed, FullTableCache cleanup queue consumes 4GB as events keeps getting added to queue (reached 28442228 for this case) for cleanup of evictionEntries. 
> There is a possibility of this due to lock used in cleanup thread, and this lock is non-fair.
>  
> !image-2024-07-18-11-17-20-894.png|width=452,height=273!
>  
> As part of this, need check if evictionEntries can be optimized as used for cache eviction when cache value is null and epoch is current value transaction Id. and/or fair locking mechanism.



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