You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Stephen O'Donnell (Jira)" <ji...@apache.org> on 2023/05/03 09:33:00 UTC

[jira] [Updated] (HDDS-8473) ReplicationManager: Clear ContainerReplicaPendingOps when RM goes to running state

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

Stephen O'Donnell updated HDDS-8473:
------------------------------------
    Summary: ReplicationManager: Clear ContainerReplicaPendingOps when RM goes to running state  (was: ReplicationManager: Investigate if ContainerReplicaPendingOps needs cleared on new leader)

> ReplicationManager: Clear ContainerReplicaPendingOps when RM goes to running state
> ----------------------------------------------------------------------------------
>
>                 Key: HDDS-8473
>                 URL: https://issues.apache.org/jira/browse/HDDS-8473
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Stephen O'Donnell
>            Assignee: Stephen O'Donnell
>            Priority: Major
>
> ContainerReplicaPendingOps contains a record of all the pending replications which are waiting to complete across the cluster. When SCM steps down as a leader, it should probably clear this table, as any of the pending commands scheduled on the DNs will be expired as soon as the new leader SCM takes over. If a failover happens and then it fails back again, we don't want to the original list of ops to be present anymore.
> As it stands, I don't think pending ops is being cleared down, so we need to investigate if it is not, and if not fix it so it does get cleared.



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