Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Sun, 25 Mar 2012 18:45:27 +0000 (UTC)
From: "Aaron T. Myers (Updated) (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <589981194.15058.1332701127296.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1156069174.15047.1332700648680.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HDFS-3145) Disallow self failover
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Aaron T. Myers updated HDFS-3145:
---------------------------------

    Affects Version/s: 0.23.2
               Status: Patch Available  (was: Open)
    
> Disallow self failover
> ----------------------
>
>                 Key: HDFS-3145
>                 URL: https://issues.apache.org/jira/browse/HDFS-3145
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: ha
>    Affects Versions: 0.23.2
>            Reporter: Eli Collins
>            Assignee: Eli Collins
>         Attachments: hdfs-3145.txt
>
>
> It is currently possible for users to make a standby NameNode failover to itself and become active. We shouldn't allow this to happen in case operators mistype and miss the fact that there are now two active NNs.
> {noformat}
> bash-4.1$ hdfs haadmin -ns ha-nn-uri -failover nn2 nn2
> Failover from nn2 to nn2 successful
> {noformat}
> After the failover above, nn2 will be 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