[
https://issues.apache.org/jira/browse/HDDS-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16591428#comment-16591428
]
Elek, Marton commented on HDDS-373:
-----------------------------------
Thanks [~dineshchitlangia] the patch.
This patch not only change the output of getconf utility but changes the
default values. I was not part of the original discussion but it also means
that the configuration values are not required any more. If that was the
intention some additional checks (such as in OmUtils.java: L69) may be removed.
I have no opinion about what is the best: provide a localhost default or
require to set the configuration. [~anu] can comment it.
Also /data/disk1/meta is not a reasonable default IMHO. /tmp/disk1/meta would
be better. (Or even better generating a value based on java.io.tmpdir to make
our osx/windows friends also happy....)
> Ozone genconf tool must generate ozone-site.xml with sample values instead of
> a template
> ----------------------------------------------------------------------------------------
>
> Key: HDDS-373
> URL: https://issues.apache.org/jira/browse/HDDS-373
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Components: Tools
> Reporter: Dinesh Chitlangia
> Assignee: Dinesh Chitlangia
> Priority: Major
> Attachments: HDDS-373.001.patch
>
>
> As discussed with [~anu], currently, the genconf tool generates a template
> ozone-site.xml. This is not very useful for new users as they would have to
> understand what values should be set for the minimal configuration properties.
> This Jira proposes to modify the ozone-default.xml which is leveraged by
> genconf tool to generate ozone-site.xml
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
