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/05/03 16:11:00 UTC
[jira] [Updated] (HDDS-6589) Add a new replication manager and change the existing one to legacy
[ https://issues.apache.org/jira/browse/HDDS-6589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Uma Maheswara Rao G updated HDDS-6589:
--------------------------------------
Parent: HDDS-6462
Issue Type: Sub-task (was: Improvement)
> Add a new replication manager and change the existing one to legacy
> -------------------------------------------------------------------
>
> Key: HDDS-6589
> URL: https://issues.apache.org/jira/browse/HDDS-6589
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Jie Yao
> Assignee: Jie Yao
> Priority: Major
> Labels: pull-request-available
>
> # 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