You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Uma Maheswara Rao G (Jira)" <ji...@apache.org> on 2022/11/10 04:20:00 UTC

[jira] [Commented] (HDDS-7057) EC: ReplicationManager - Over replication handler should set repIndex on delete cmds

    [ https://issues.apache.org/jira/browse/HDDS-7057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17631444#comment-17631444 ] 

Uma Maheswara Rao G commented on HDDS-7057:
-------------------------------------------

Just changed the reporter as per Nilotpal request as he found this issue.

> EC: ReplicationManager - Over replication handler should set repIndex on delete cmds
> ------------------------------------------------------------------------------------
>
>                 Key: HDDS-7057
>                 URL: https://issues.apache.org/jira/browse/HDDS-7057
>             Project: Apache Ozone
>          Issue Type: Sub-task
>          Components: SCM
>            Reporter: Nilotpal Nandi
>            Assignee: Stephen O'Donnell
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.3.0
>
>
> ContainerReplicaPendingOps needs to track the replica index of any pending replicas. In ECOverReplicationHandler we missed setting the repIndex of the replica in the delete command.



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