Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Date: Sun, 20 May 2012 06:18:41 +0000 (UTC)
From: "Todd Lipcon (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: <1595989777.739.1337494721721.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <1039781767.24299.1333732283213.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (HDFS-3217) ZKFC should restart NN when
 healthmonitor gets a SERVICE_NOT_RESPONDING exception
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Todd Lipcon resolved HDFS-3217.
-------------------------------

    Resolution: Won't Fix

We had some offline discussion about this and it seems like folks are on board with the current design (i.e. that the failover controller doesn't directly launch or restart the namenode). We can revisit in the future should the current design prove problematic. Resolving as wontfix for now.
                
> ZKFC should restart NN when healthmonitor gets a SERVICE_NOT_RESPONDING exception
> ---------------------------------------------------------------------------------
>
>                 Key: HDFS-3217
>                 URL: https://issues.apache.org/jira/browse/HDFS-3217
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: auto-failover, ha
>            Reporter: Hari Mankude
>            Assignee: Hari Mankude
>


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