You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Arpit Agarwal (Jira)" <ji...@apache.org> on 2020/06/02 18:39:00 UTC
[jira] [Updated] (HDDS-1760) Avoid using
DFS_CONTAINER_RATIS_ENABLED_KEY to find replication factor and type
[ https://issues.apache.org/jira/browse/HDDS-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arpit Agarwal updated HDDS-1760:
--------------------------------
Target Version/s: 0.7.0
> 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: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Bharat Viswanadham
> Assignee: 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.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org