Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Tue, 13 Dec 2011 03:05:32 +0000 (UTC)
From: "Aaron T. Myers (Updated) (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <1044857844.4202.1323745532463.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1824706802.52459.1323323500158.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HADOOP-7896) HA: if both NNs are in Standby mode,
 client needs to try failing back and forth several times with sleeps
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Aaron T. Myers updated HADOOP-7896:
-----------------------------------

    Attachment: HADOOP-7896-HDFS-1623.patch

Here's a patch which addresses the issue.
                
> HA: if both NNs are in Standby mode, client needs to try failing back and forth several times with sleeps
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-7896
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7896
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: ipc
>    Affects Versions: HA Branch (HDFS-1623)
>            Reporter: Todd Lipcon
>            Assignee: Aaron T. Myers
>            Priority: Critical
>         Attachments: HADOOP-7896-HDFS-1623.patch
>
>
> For a manual failover, there may be an intermediate state for a non-trivial amount of time where both NNs are in standby mode. Currently, the failover proxy will immediately failover on receiving this exception from the first NN, and when it hits the same exception on the second NN, it immediately fails. It should probably fail back and forth nearly indefinitely if both NNs are in Standby mode.

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