[
https://issues.apache.org/jira/browse/HADOOP-7510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095398#comment-13095398
]
Daryn Sharp commented on HADOOP-7510:
-------------------------------------
Sorry, forgot to address the other point:
bq. This seems to be fragile because InetSocketAddress API doesn't gaurantee
that dns lookup will not be invoked.
I researched this very thoroughly:
* {{InetSocketAddress}} does not perform any lookups of its own. It delegates
to the contained {{InetAddress}}.
* An {{InetAddress}} only resolves an ip if the host field is null.
* If the {{InetAddress}} is instantiated with an explicit host string and ip,
then the host field is not null, so it will just return that host. No lookup
occurs.
* Hence, instantiating an {{InetSocketAddress}} with a explicitly constructed
{{InetAddress}} with both host/ip will guarantee that {{getHostName}} will not
perform a lookup.
> Tokens should use original hostname provided instead of ip
> ----------------------------------------------------------
>
> Key: HADOOP-7510
> URL: https://issues.apache.org/jira/browse/HADOOP-7510
> Project: Hadoop Common
> Issue Type: Improvement
> Components: security
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Fix For: 0.20.205.0
>
> Attachments: HADOOP-7510.patch
>
>
> Tokens currently store the ip:port of the remote server. This precludes
> tokens from being used after a host's ip is changed. Tokens should store the
> hostname used to make the RPC connection. This will enable new processes to
> use their existing tokens.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
