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/08/17 19:13:00 UTC

[jira] [Resolved] (HDDS-668) Replica Manager should use replica with latest delete transactionID

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

Stephen O'Donnell resolved HDDS-668.
------------------------------------
    Resolution: Won't Fix

Closing this for now. As discussed, we need a wider solution for this that is not part of Replication Manager.

> Replica Manager should use replica with latest delete transactionID
> -------------------------------------------------------------------
>
>                 Key: HDDS-668
>                 URL: https://issues.apache.org/jira/browse/HDDS-668
>             Project: Apache Ozone
>          Issue Type: Bug
>            Reporter: Lokesh Jain
>            Assignee: Stephen O'Donnell
>            Priority: Major
>
> Currently replica manager does not use delete trasactionID for choosing the replica which will be replicated. This Jira aims to store delete transactionID for each replica so that replica manager can choose replica with latest delete transactionID.



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