You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "dhruba borthakur (JIRA)" <ji...@apache.org> on 2007/10/04 20:24:50 UTC

[jira] Resolved: (HADOOP-1605) Automatic namenode restart when it encounters an error situation

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

dhruba borthakur resolved HADOOP-1605.
--------------------------------------

       Resolution: Won't Fix
    Fix Version/s:     (was: 0.15.0)

System administrators already employ some means to detect if a server is disappears, and restarts it automatically if need be. Especially because they have to administer may different types of servers/applications. I am closing this issue as "won't fix".

> Automatic namenode restart when it encounters an error situation
> ----------------------------------------------------------------
>
>                 Key: HADOOP-1605
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1605
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: dfs
>            Reporter: dhruba borthakur
>            Assignee: dhruba borthakur
>         Attachments: namenodeRestart4.patch, watcher.patch
>
>
> The namenode dies when it encounters an unexpected Runtime Exception. Instead, it can catch exceptions, clears up all its internal data structures and restarts. This was attempted in HADOOP-1486 earlier.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.