[
https://issues.apache.org/jira/browse/HDFS-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13770133#comment-13770133
]
Joep Rottinghuis commented on HDFS-5221:
----------------------------------------
We're thinking of two approaches:
1) Fixing the hdfs-client when the hftp is used to use a retry mechanism to
fail over to the active NN
2) Use URL re-direction from the standby to the active NN.
Advantage of 1) is that it will work even if the (previously) active NN host is
completely down, or if the NN process is not running at all.
Advantage of 2) is that it will give _some_ benefits / resilience, even if
Hadoop 1.0 clients are not modified.
> hftp: does not work with HA NN configuration
> --------------------------------------------
>
> Key: HDFS-5221
> URL: https://issues.apache.org/jira/browse/HDFS-5221
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ha, hdfs-client
> Affects Versions: 2.0.5-alpha
> Reporter: Joep Rottinghuis
> Priority: Blocker
>
> When copying data between clusters of significant different version (say from
> Hadoop 1.x equivalent to Hadoop 2.x) we have to use hftp.
> When HA is configured, you have to point to a single (active) NN.
> Now, when the active NN becomes standby, the the hftp: addresses will fail.
--
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
