[
https://issues.apache.org/jira/browse/HADOOP-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525800
]
dhruba borthakur commented on HADOOP-1605:
------------------------------------------
On second thoughts, if the namenode catches exceptions and restarts, it still
does not prevent the case when then JVM encounters a fault and exits.
A better approach would be to have a WatchNode process that is told to monitor
the Namenode. If the Namenode process exits, then the WatchNode process will
restart the Namenode. A WatchNode process could be configured to watch multiple
servers (Namenode, DataNode, Secondarynamenode, JobTracker, etc).
> 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
> Fix For: 0.15.0
>
> Attachments: namenodeRestart4.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.
