[
https://issues.apache.org/jira/browse/HDFS-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262498#comment-13262498
]
nemon lou commented on HDFS-161:
--------------------------------
I prefer the "ignored directories that do not exist " feature.
When each machine has its own disk space configuration,it's fine to configure
all possible directories in the master's "dfs-site.xml" file and then simply
copy it to slaves to avoid configuring it on each machine.
In most cases,what matters is the disk which you mount on. So mkdir dose't make
sense especially when making many directories on the same disk.
> DataNode will create missing dfs.data.dir directories contrary to docs
> ----------------------------------------------------------------------
>
> Key: HDFS-161
> URL: https://issues.apache.org/jira/browse/HDFS-161
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: data-node, documentation
> Reporter: Todd Lipcon
> Priority: Minor
> Labels: newbie
>
> The documentation (and HADOOP-340) seems to indicate that if a data dir
> listed in dfs.data.dir does not exist, it will be ignored. In fact, if the
> hadoop user has access to (essentially) mkdir -p the data dir it will do so.
> I'd like to add another configuration parameter, perhaps dfs.data.dir.create
> with default true (to not break any existing tutorials). If this is set to
> false then data dirs that do not exist will not implicitly be created.
> The motivation for this is the same as HADOOP-340 - we have different disk
> configs in our cluster and hadoop is creating data dirs where we do not want
> them.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
