hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2179) HA: namenode fencing mechanism
Date Thu, 04 Aug 2011 16:59:27 GMT

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

Todd Lipcon commented on HDFS-2179:

The only difference the lack of {{continue}} statement makes should be logging output. But
I see your point - I'll add a {{continue}} there to be consistent, and then commit this to
the HA branch.

> HA: namenode fencing mechanism
> ------------------------------
>                 Key: HDFS-2179
>                 URL: https://issues.apache.org/jira/browse/HDFS-2179
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: name-node
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>         Attachments: 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message