[ 
https://issues.apache.org/jira/browse/HDFS-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13999019#comment-13999019
 ] 

Hudson commented on HDFS-2949:
------------------------------

SUCCESS: Integrated in Hadoop-trunk-Commit #5605 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/5605/])
HDFS-2949. Add check to active state transition to prevent operator-induced 
split brain. Contributed by Rushabh S Shah. (kihwal: 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1594709)
* 
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ha/HAAdmin.java
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNode.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/tools/DFSHAAdmin.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/tools/TestDFSHAAdmin.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/tools/TestDFSHAAdminMiniCluster.java


> 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
>             Fix For: 3.0.0, 2.5.0
>
>         Attachments: HDFS-2949-v2.patch, HDFS-2949-v3.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)

Reply via email to