[
https://issues.apache.org/jira/browse/HDDS-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17650611#comment-17650611
]
mingchao zhao commented on HDDS-1760:
-------------------------------------
Ozone 1.3.0 had been released and we currently have more than 600 open issues
targeted for 1.3.0. I am moving the target field to 1.4.0.
If there is anything needs to be discussed about the Target Version, Please
reach out to me via Apache email or Slack.
> Avoid using DFS_CONTAINER_RATIS_ENABLED_KEY to find replication factor and
> type
> -------------------------------------------------------------------------------
>
> Key: HDDS-1760
> URL: https://issues.apache.org/jira/browse/HDDS-1760
> Project: Apache Ozone
> Issue Type: Bug
> Reporter: Bharat Viswanadham
> Priority: Major
>
> In OzoneManager, when trying to createFile, createKey when the user has not
> passed replication type and factor, we use dfs.container.ratis.enabled to set
> default replication type and factor.
>
> If this property (dfs.container.ratis.enabled) is set to false, we use
> replication type as standalone and replication factor as 1. If it is true,
> use replication type as RATIS and factor as 3.
>
> I think now this is not correct, as now with RATIS type we can have both
> replication factor 1 and 3.
>
> *The proposal is to change as below.*
> 1. Eliminate the above property.
> 2. If the replication type and replication factor are not set the default to
> RATIS and one.
>
> The second alternative is to make these parameters mandatory. But that
> changes the current behavior. And this breaks compatibility between old
> release.
>
> This Jira is created based on [~arpaga] comment during the review of HDDS-1731
> Or any other suggestions to solve this issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
