You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Janus Chow (Jira)" <ji...@apache.org> on 2023/12/16 23:44:05 UTC
[jira] [Updated] (HDDS-7762) Rename Replication Manager to RedundancyManager
[ https://issues.apache.org/jira/browse/HDDS-7762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Janus Chow updated HDDS-7762:
-----------------------------
Target Version/s: 1.5.0 (was: 1.4.0)
I am managing the 1.4.0 release and we currently have more than 500 issues targeted for 1.4.0. I am moving the target field to 1.5.0.
If you are actively working on this jira and believe this should be targeted for the 1.4.0 release, Please reach out to me via Apache email or Slack.
> Rename Replication Manager to RedundancyManager
> -----------------------------------------------
>
> Key: HDDS-7762
> URL: https://issues.apache.org/jira/browse/HDDS-7762
> Project: Apache Ozone
> Issue Type: Improvement
> Components: SCM
> Affects Versions: 1.3.0
> Reporter: Uma Maheswara Rao G
> Priority: Minor
>
> Currently we have ReplicationManager class in SCM which is a very important module in it. Even though it does not have any exposed interfaces to users, we talk a lot about it. With addition is EC, it is not really a replication, it is redundancy. It make sense for Ratis to have ReplicationManager. We need a common name for both, it is a good idea to rename it to RedundancyManager.
> Risk: Low risk of renaming it.
> Impact: Changes may be more and hence it could impact any branch merges or other Jira merges.
> So, to keep less impact, I would suggest to start taking this step by step towards better naming eventually.
> Thoughts?
--
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