[ https://issues.apache.org/jira/browse/HDFS-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122381#comment-13122381 ]
Hadoop QA commented on HDFS-1973: --------------------------------- +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12498050/HDFS-1973-HDFS-1623.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 2 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in . +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/1346//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/1346//console This message is automatically generated. > HA: HDFS clients must handle namenode failover and switch over to the new > active namenode. > ------------------------------------------------------------------------------------------ > > Key: HDFS-1973 > URL: https://issues.apache.org/jira/browse/HDFS-1973 > Project: Hadoop HDFS > Issue Type: Sub-task > Reporter: Suresh Srinivas > Assignee: Aaron T. Myers > Attachments: HDFS-1973-HDFS-1623.patch, HDFS-1973-HDFS-1623.patch, > HDFS-1973-HDFS-1623.patch, HDFS-1973-HDFS-1623.patch, > HDFS-1973-HDFS-1623.patch, HDFS-1973-HDFS-1623.patch, > HDFS-1973-HDFS-1623.patch, hdfs-1973.0.patch > > > During failover, a client must detect the current active namenode failure and > switch over to the new active namenode. The switch over might make use of IP > failover or some thing more elaborate such as zookeeper to discover the new > active. -- 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