You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ozone.apache.org by "Jie Yao (Jira)" <ji...@apache.org> on 2022/04/25 12:29:00 UTC

[jira] [Updated] (HDDS-6589) Add a new replication manager and make the existing one legacy

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

Jie Yao updated HDDS-6589:
--------------------------
    Summary: Add a new replication manager and make the existing one legacy  (was: Add replication manager V2)

> Add a new replication manager and make the existing one legacy
> --------------------------------------------------------------
>
>                 Key: HDDS-6589
>                 URL: https://issues.apache.org/jira/browse/HDDS-6589
>             Project: Apache Ozone
>          Issue Type: Improvement
>            Reporter: Jie Yao
>            Assignee: Jie Yao
>            Priority: Major
>
> # Rename the existing RM class to LegacyReplicationManager, and expose the processContainer() method as protected or public. Remove the scheduling from this RM.
>  # Create a new replication Manager, called ReplicationManager, then have it scheduled periodically like the current one.
>  # When the new RM processes a container, if it is EC, it goes down the new path. If it is not EC, we call LegacyReplicationManager.processContainer(...).



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org