Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Mon, 30 Jan 2012 04:27:10 +0000 (UTC)
From: "Eli Collins (Updated) (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <996211716.6591.1327897630205.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <203174699.37875.1324521330677.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HADOOP-7938) HA: the FailoverController should
 optionally fence the active during failover
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Eli Collins updated HADOOP-7938:
--------------------------------

    Attachment: hadoop-7938.txt

Patched rebased on the tip of branch post HDFS-2841.
                
> HA: the FailoverController should optionally fence the active during failover
> -----------------------------------------------------------------------------
>
>                 Key: HADOOP-7938
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7938
>             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-7938.txt, hadoop-7938.txt, hadoop-7938.txt, hadoop-7938.txt
>
>
> The FailoverController in HADOOP-7924 needs to be able to fence off the current active in case it fails to transition to standby (or the user requests it for sanity). This is needed even for manual failover (the CLI should use the configured fencing mechanism). The FC needs to access the HDFS-specific implementations HDFS-2179, could add a common fencing interface (or just shell out but we may not always want to do that).

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