hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HDFS-3217) ZKFC should restart NN when healthmonitor gets a SERVICE_NOT_RESPONDING exception
Date Sun, 20 May 2012 06:18:41 GMT

     [ 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

        

Mime
View raw message