[
https://issues.apache.org/jira/browse/HADOOP-7510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095386#comment-13095386
]
Daryn Sharp commented on HADOOP-7510:
-------------------------------------
As far as I can tell, there isn't a compat issue with any permutation of
new/old. Hftp requests appear to be handled as follows:
# The client requests a token from the NN. The NN will return a token with a
service its format (ip:port or host:port).
# The client doesn't care about the NN's service format. It resets the token's
service to format it uses.
# To read a file, the client sends the token to the NN. The NN doesn't care
about the token's service format. It just redirects the client to a DN with
the unchanged token.
# The DN doesn't care about the client's service format either. The DN resets
the token's service to its format, and then the DFSClient connects to the NN
using its format. The connection succeeds since the format is equal between
the connection addr and the token's service.
Am I overlooking something?
> 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
