[
https://issues.apache.org/jira/browse/HDDS-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Viswanadham updated HDDS-1760:
-------------------------------------
Description:
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.
Or any other suggestions to solve this issue.
was:
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.
Any other suggestions to solve this issue.
> 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.
>
> Or any other suggestions to solve this issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
