[
https://issues.apache.org/jira/browse/HADOOP-7510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100551#comment-13100551
]
Jitendra Nath Pandey commented on HADOOP-7510:
----------------------------------------------
> New tasks spawned after the ip change will fail.
Good point. The alternative approach doesn't work.
My concerns with the posted patch:
1) The use-case mentioned earlier (the contrived one) doesn't work.
2) The assumption about InetSocketAddress#getHostname is not a documented API
behavior. Different java implementations could do it differently.
3) This is a risky change.
A safer approach, in my opinion, will be to make this change in a major
release (e.g. 23) where some backward compatibility constraints can probably be
relaxed. That will allow us a better fix using standard java api.
> 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-2.patch, HADOOP-7510-3.patch,
> 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
