[
https://issues.apache.org/jira/browse/HADOOP-7896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13219170#comment-13219170
]
Hudson commented on HADOOP-7896:
--------------------------------
Integrated in Hadoop-Hdfs-HAbranch-build #92 (See
[https://builds.apache.org/job/Hadoop-Hdfs-HAbranch-build/92/])
HADOOP-8116. RetriableCommand is using RetryPolicy incorrectly after
HADOOP-7896. Contributed by Aaron T. Myers. (Revision 1294729)
Result = UNSTABLE
atm : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1294729
Files :
*
/hadoop/common/branches/HDFS-1623/hadoop-common-project/hadoop-common/CHANGES.HDFS-1623.txt
*
/hadoop/common/branches/HDFS-1623/hadoop-tools/hadoop-distcp/src/main/java/org/apache/hadoop/tools/util/RetriableCommand.java
*
/hadoop/common/branches/HDFS-1623/hadoop-tools/hadoop-distcp/src/test/java/org/apache/hadoop/tools/mapred/TestCopyMapper.java
> HA: if both NNs are in Standby mode, client needs to try failing back and
> forth several times with sleeps
> ---------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-7896
> URL: https://issues.apache.org/jira/browse/HADOOP-7896
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: ha, ipc
> Affects Versions: HA Branch (HDFS-1623)
> Reporter: Todd Lipcon
> Assignee: Aaron T. Myers
> Priority: Critical
> Fix For: HA Branch (HDFS-1623)
>
> Attachments: HADOOP-7896-HDFS-1623.patch,
> HADOOP-7896-HDFS-1623.patch, HADOOP-7896-HDFS-1623.patch
>
>
> For a manual failover, there may be an intermediate state for a non-trivial
> amount of time where both NNs are in standby mode. Currently, the failover
> proxy will immediately failover on receiving this exception from the first
> NN, and when it hits the same exception on the second NN, it immediately
> fails. It should probably fail back and forth nearly indefinitely if both NNs
> are in Standby mode.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
