Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Date: Fri, 3 Feb 2012 19:47:53 +0000 (UTC)
From: "Todd Lipcon (Resolved) (JIRA)" <jira@apache.org>
To: common-dev@hadoop.apache.org
Message-ID: 
 <1725678159.8700.1328298473924.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <179411052.75421.1327459721376.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (HADOOP-7991) HA: the FailoverController should
 check the standby is ready before failing over
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Todd Lipcon resolved HADOOP-7991.
---------------------------------

       Resolution: Fixed
    Fix Version/s: HA Branch (HDFS-1623)
     Hadoop Flags: Reviewed

Eli committed this yesterday, but was having JIRA problems. Resolving on his behalf.
                
> HA: the FailoverController should check the standby is ready before failing over
> --------------------------------------------------------------------------------
>
>                 Key: HADOOP-7991
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7991
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: ha
>    Affects Versions: HA Branch (HDFS-1623)
>            Reporter: Eli Collins
>            Assignee: Eli Collins
>             Fix For: HA Branch (HDFS-1623)
>
>         Attachments: hadoop-7991.txt
>
>
> The FC in preFailoverChecks should check that the target service is ready for failover (eg in the case of HDFS, that it's not in SM) before failing over to it. We'll need to provide a force option as well since the standby may not actually be ready until the failover has been initiated (eg because becoming active kicks it to check the log and see newly allocated blocks).

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