[
https://issues.apache.org/jira/browse/HDFS-12532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16218767#comment-16218767
]
Daryn Sharp commented on HDFS-12532:
------------------------------------
This is very unorthodox use case that I'm not convinced is worth "fixing". DN
is running on the NN. No dns. DN principal contains a hostname the node
itself cannot resolve. This makes no sense because:
# I don't think kerberos will even work without dns and/or /etc/hosts entries.
# The NN performs principal hostname authorization for the DN protocol. That
should fail unless also turned off?
# Spnego doesn't work with ips which means the HA NNs shouldn't be able to
communicate.
# The host file reader for the allow/deny ignores unresolvable addresses.
I feel the stated problem has been over generalized. What is the specific
issue you encountered? A transient misconfigured dns entry or /etc/hosts entry?
> 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
> Attachments: HDFS-12532.patch
>
>
> Configure principal without hostname (i.e hdfs/[email protected])
> 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: [email protected]
For additional commands, e-mail: [email protected]
