You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Eli Collins (Moved) (JIRA)" <ji...@apache.org> on 2012/01/06 21:06:40 UTC

[jira] [Moved] (HADOOP-7961) HA: namenode fencing mechanism

     [ https://issues.apache.org/jira/browse/HADOOP-7961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eli Collins moved HDFS-2179 to HADOOP-7961:
-------------------------------------------

      Component/s:     (was: name-node)
                   ha
    Fix Version/s:     (was: HA branch (HDFS-1623))
                   HA Branch (HDFS-1623)
              Key: HADOOP-7961  (was: HDFS-2179)
          Project: Hadoop Common  (was: Hadoop HDFS)
    
> HA: namenode fencing mechanism
> ------------------------------
>
>                 Key: HADOOP-7961
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7961
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: ha
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>             Fix For: HA Branch (HDFS-1623)
>
>         Attachments: hdfs-2179.txt, hdfs-2179.txt, hdfs-2179.txt
>
>
> In an HA cluster, when there are two NNs, the invariant that only one NN is active at a time has to be preserved in order to prevent "split brain syndrome." Thus, when a standby NN is transition to "active" state during a failover, it needs to somehow _fence_ the formerly active NN to ensure that it can no longer perform edits. This JIRA is to discuss and implement NN fencing.

--
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