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

Daryn Sharp commented on HDFS-12532:
------------------------------------

For starters, the exception has nothing to do with kerberos.  You will get the 
same exception regardless of the security setting.

bq. Configure principal without hostname (i.e hdfs/had...@hadoop.com)
That principal does have a hostname.  Did you mean h...@hadoop.com?

bq. Configure floatingIP
Is floating ip a dynamic dhcp address?  If yes, is this for testing? Anyway, I 
need to understand more about X.Y.Y.1 and X.Y.Y.100.  I'm assuming X.Y.Y.1 is 
localhost/127.0.0.1?  X.Y.Y.100 is the dhcp assigned address?

Here's the problem with your proposal:  "getLocalHost" will attempt to resolve 
the system assigned hostname, which you are assuming will always be in 
/etc/hosts, but falls back to localhost.  So let's say that the hostname 
doesn't resolve though – intentional or not – which forces a bind to localhost 
which isn't going to be able to connect to anything external.  Might work well 
for testing on a single node cluster when it doesn't matter if the host uses 
its public interface or localhost to connect to itself, but not for general use.

I'd rather see the NN squawking about unresolvable addresses than DNs silently 
failing to connect because they are binding to localhost.  It would also 
cripple other rpc clients whose servers don't care about dns at all.

I also not keen on having more confs w/o having a clearly stated use case.

> DN Reg can Fail when principal doesn't contain hostname and floatingIP is 
> configured.
> -------------------------------------------------------------------------------------
>
>                 Key: HDFS-12532
>                 URL: https://issues.apache.org/jira/browse/HDFS-12532
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Brahma Reddy Battula
>            Assignee: Brahma Reddy Battula
>
> Configure principal without hostname (i.e hdfs/had...@hadoop.com)
> Configure floatingIP
> Start Cluster.
> Here DN will fail to register as it can take IP which is not in "/etc/hosts".



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to