[jira] [Resolved] (HDDS-1581) Atleast one of the metadata dir config property must be tagged as REQUIRED

["Anu Engineer (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HDDS-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anu Engineer resolved HDDS-1581.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 0.4.1

[~bharatviswa] and [~xyao] Thanks for the reviews and comments. [~dineshchitlangia] Thanks for the contribution. I have committed this patch to the trunk.

> Atleast one of the metadata dir config property must be tagged as REQUIRED
> --------------------------------------------------------------------------
>
>                 Key: HDDS-1581
>                 URL: https://issues.apache.org/jira/browse/HDDS-1581
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>    Affects Versions: 0.4.0
>            Reporter: Dinesh Chitlangia
>            Assignee: Dinesh Chitlangia
>            Priority: Major
>              Labels: configuration, pull-request-available
>             Fix For: 0.4.1
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> This issue was discovered while working on HDDS-373 to generate a minimal ozone-site.xml with required values.
> {panel:title=ozone-default.xml}
> <property>
>     <name>ozone.metadata.dirs</name>
>     <value/>
>     <tag>OZONE, OM, SCM, CONTAINER, STORAGE</tag>
>     <description>
>       This setting is the fallback location for SCM, OM and DataNodes
>       to store their metadata. This setting may be used in test/PoC clusters
>       to simplify configuration.
>       For production clusters or any time you care about performance, it is
>       recommended that ozone.om.db.dirs, ozone.scm.db.dirs and
>       dfs.container.ratis.datanode.storage.dir be configured separately.
>     </description>
>   </property>
> {panel}
> However, none of the properties listed above are tagged as REQUIRED.
> For starters, as the goal of HDDS-373 is to generate a simple minimal ozone-site.xml that can be used to start ozone, I propose that we do either of the following:
> 1. Tag ozone.metadata.dirs as REQUIRED 
> OR
> 2. Tag ozone.om.db.dirs, ozone.scm.db.dirs and dfs.container.ratis.datanode.storage.dir as REQUIRED
> For simplicity, I would prefer option 1 as that is the fallback config. We have already stated that for production use, we must defined the granular properties instead of relying on this fallback property ozone.metadata.dirs
> As advised by [~xyao], we are going with Option 1 and adding more details to description of other metadata related properties that would use ozone.metadata.dirs as a fallback.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org