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/03/30 16:50:00 UTC

[jira] [Commented] (HDDS-8109) Consider seperating Ratis and EC MisReplication Handling

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

Stephen O'Donnell commented on HDDS-8109:
-----------------------------------------

Please review the description in HDDS-8335 before starting on this one, as it may influence how you restructure things.

> Consider seperating Ratis and EC MisReplication Handling
> --------------------------------------------------------
>
>                 Key: HDDS-8109
>                 URL: https://issues.apache.org/jira/browse/HDDS-8109
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Stephen O'Donnell
>            Assignee: Attila Doroszlai
>            Priority: Major
>
> Ratis and EC MisReplication and handled in separate classes, but they share a common parent class MisReplicationHandler. In it, there is logic to create the replication commands (createReplicateCommands() ), where it gets a list of replicas to be copied and new targets.
> For EC, you must copy a specific replica index from A to B, but for Ratis, all replicas are the same. When you have load limiting in place, we really want to copy from the least loaded source. It probably makes sense to split Ratis handling from EC handling here, as they are quite different.



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