[
https://issues.apache.org/jira/browse/HDFS-4783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated HDFS-4783:
--------------------------------
Resolution: Fixed
Fix Version/s: 2.1.0-beta
3.0.0
Status: Resolved (was: Patch Available)
I committed this to trunk, branch-2, and branch-2.1-beta. Thanks to Chuan and
Daryn for reviews.
[~daryn], let me take a stab at describing the underlying issue that you
mentioned:
# {{NameNode#initialize}} starts initializing namenode from given
{{Configuration}}.
# {{NameNodeRpcServer}} constructor builds RPC server, binding to address
specified in {{Configuration}}. Resulting address may differ from what is in
{{Configuration}} if using any address (0.0.0.0) or ephemeral port.
# {{NameNodeRpcServer}} then sets value of address back in {{Configuration}} to
the real resulting address. By side effect, the forward lookup and then
reverse lookup may result in an unexpected hostname in {{Configuration}}, if
there are multiple names for the host (i.e. CNAME records).
Does this accurately describe what you had in mind? If so, let me know, and
I'll paste it into a new issue.
I'm not yet sure what we could do about it, but it might help to start tracking
it. I recently saw this behavior cause some confusion for a deployment that
was resolving the NN to an unexpected address.
> TestDelegationTokensWithHA#testHAUtilClonesDelegationTokens fails on Windows
> ----------------------------------------------------------------------------
>
> Key: HDFS-4783
> URL: https://issues.apache.org/jira/browse/HDFS-4783
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: test
> Affects Versions: 3.0.0, 2.1.0-beta
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Fix For: 3.0.0, 2.1.0-beta
>
> Attachments: HDFS-4783.1.patch
>
>
> This test asserts that delegation tokens previously associated to a host with
> a resolved IP address no longer match for selection when
> hadoop.security.token.service.use_ip is set false. The test assumes that
> 127.0.0.1 resolves to host name "localhost". On Windows, this is not the
> case, and instead it resolves to "127.0.0.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
