[
https://issues.apache.org/jira/browse/HDFS-3977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13463333#comment-13463333
]
Todd Lipcon commented on HDFS-3977:
-----------------------------------
Hi Arpit. This was explicitly changed in HDFS-3446 and marked there as
Incompatible. I think it is much better to error on startup with a meaningful
error message than to silently ignore the file when it can't be read. The issue
with having just a WARN is that most admins won't notice, given our logging is
so noisy.
> Incompatible change between hadoop-1 and hadoop-2 when the dfs.hosts and
> dfs.hosts.exclude files are not present
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-3977
> URL: https://issues.apache.org/jira/browse/HDFS-3977
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.0.2-alpha
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
>
> While testing hadoop-1 and hadoop-2 the following was noticed
> if the files in the properties dfs.hosts and dfs.hosts.exclude do not exist
> in hadoop-1 namenode format and start went through successfully.
> in hadoop-2 we get a file not found exception and both the format and the
> namenode start commands fail.
> We should be logging a warning in the case when the file is not found so that
> we are compatible with hadoop-1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
