[ https://issues.apache.org/jira/browse/HDFS-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13982212#comment-13982212 ]
Hadoop QA commented on HDFS-2949: --------------------------------- {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12642104/HDFS-2949-v2.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 2 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. There were no new javadoc warning messages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 1.3.9) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs. {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/6749//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/6749//console This message is automatically generated. > HA: Add check to active state transition to prevent operator-induced split > brain > -------------------------------------------------------------------------------- > > Key: HDFS-2949 > URL: https://issues.apache.org/jira/browse/HDFS-2949 > Project: Hadoop HDFS > Issue Type: Improvement > Components: ha, namenode > Affects Versions: 0.24.0 > Reporter: Todd Lipcon > Assignee: Rushabh S Shah > Attachments: HDFS-2949-v2.patch, HDFS-2949.patch > > > Currently, if the administrator mistakenly calls "-transitionToActive" on one > NN while the other one is still active, all hell will break loose. We can add > a simple check by having the NN make a getServiceState() RPC to its peer with > a short (~1 second?) timeout. If the RPC succeeds and indicates the other > node is active, it should refuse to enter active mode. If the RPC fails or > indicates standby, it can proceed. > This is just meant as a preventative safety check - we still expect users to > use the "-failover" command which has other checks plus fencing built in. -- This message was sent by Atlassian JIRA (v6.2#6252)