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

Posted to issues@ozone.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/09/20 08:15:00 UTC

[jira] [Updated] (HDDS-7232) Introduce container level lock while handling container report events by SCM and Recon

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

ASF GitHub Bot updated HDDS-7232:
---------------------------------
    Labels: pull-request-available  (was: )

> Introduce container level lock while handling container report events by SCM and Recon
> --------------------------------------------------------------------------------------
>
>                 Key: HDDS-7232
>                 URL: https://issues.apache.org/jira/browse/HDDS-7232
>             Project: Apache Ozone
>          Issue Type: Improvement
>          Components: Ozone Recon
>            Reporter: Devesh Kumar Singh
>            Assignee: Devesh Kumar Singh
>            Priority: Major
>              Labels: pull-request-available
>
> *Introduce container level lock while handling container report events by SCM and Recon*
> By using container level locks in events handling of Container Reports by SCM and Recon will minimize the thread lock contention and starvation issue. Currently it.is global read write lock in ContainerStateManagerImpl class.



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