Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Sun, 25 Mar 2012 19:33:26 +0000 (UTC)
From: "Hadoop QA (Commented) (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <1211978411.15123.1332704007010.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HADOOP-8208) Disallow self failover
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hadoop QA commented on HADOOP-8208:
-----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12519870/hdfs-3145.txt
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 3 new or modified tests.

    -1 patch.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/776//console

This message is automatically generated.
                
> Disallow self failover
> ----------------------
>
>                 Key: HADOOP-8208
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8208
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: ha
>            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