[
https://issues.apache.org/jira/browse/HDFS-5237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13775898#comment-13775898
]
Eli Collins commented on HDFS-5237:
-----------------------------------
Agree it's reasonable to validate dfs.datanode.hostname, but Junping's patch
removes this config option which will break some configurations that use
HDFS-3150 and need to set the reported hostname to something other than the
default (for example if getDefaultHost returns a hostname on network A and the
clients want to talk to the DN via network B). Shall we re-purpose this to add
dfs.datanode.hostname validation?
> Get rid of nodes' registration names
> ------------------------------------
>
> Key: HDFS-5237
> URL: https://issues.apache.org/jira/browse/HDFS-5237
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Junping Du
> Fix For: 3.0.0
>
> Attachments: HDFS-5237.patch
>
>
> Per discussion in HDFS-5208 and may be some other discussions before, Node's
> registration name is pretty confusing and shouldn't be used in production
> environment as topology resolving issues. So we remove related configuration
> dfs.datanode.hostname or its old one "slave.host.name".
--
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
