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 2023/02/22 11:59:00 UTC

[jira] [Updated] (HDDS-8008) Move pendingOps into ContainerStateManagerImpl to ensure consistent state

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

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

> Move pendingOps into ContainerStateManagerImpl to ensure consistent state
> -------------------------------------------------------------------------
>
>                 Key: HDDS-8008
>                 URL: https://issues.apache.org/jira/browse/HDDS-8008
>             Project: Apache Ozone
>          Issue Type: Sub-task
>          Components: SCM
>            Reporter: Stephen O'Donnell
>            Assignee: Stephen O'Donnell
>            Priority: Major
>              Labels: pull-request-available
>
> As things stand, ContainerManagerImpl holds a reference to ContainerReplicaPendingOps. As new replicas are received or deleted from the DNs, the replicas are updated in ContainerStateManager under a lock, and then pending ops is updated. This leave the possibility of a race condition where the replicas have been updated but pending ops has not.
> To avoid this, we should move the pendingOps update into the StateManager so it is updated along with the replicas under the same lock.



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