hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Zeyliger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5237) Get rid of nodes' registration names
Date Fri, 20 Sep 2013 15:25:57 GMT

    [ https://issues.apache.org/jira/browse/HDFS-5237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13773074#comment-13773074
] 

Philip Zeyliger commented on HDFS-5237:
---------------------------------------

I don't think this is a great idea.  Hadoop's not been great at separating out a few things:

* The bind addresses and ports for RPC and HTTP.  (Particularly whether to bind on 0.0.0.0
or on a single IP.)
* The way to identify this process to other people so that they can reach it
* How to use DNS to reach other folks

There are, I agree, very minimal defaults here.  Bind to the wildcard.  Identify as {{hostname
-f}}.  Use default DNS settings.  Don't talk to DNS explicitly but use the normal OS ways
to do it.

{{slave.host.name}} has, I think, made it possible to do some less frequent but still important
configurations.  I see this most often as a host having 2 names ("management-name" and "data-name")
where "management-name" is the one that's hostname.  I've seen it in use in real configurations
(not just in tests) where it did the trick.

Meanwhile, {{DNS.getHosts(String strInterface, String nameserver)}} is a very odd way to configure
the hostname that a process should identify as.  It says, "hey, use this other system and
do a reverse lookup for yourself with these parameters."  Most of the time, though, when you're
in this case, you're already generating your configuration from something that knows exactly
what IP/name you want, and it would be simpler and less error-prone to just specify it.

Cheers,

Philip

                
> 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
>            Assignee: 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

Mime
View raw message