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 "Steve Loughran (JIRA)" <ji...@apache.org> on 2009/01/16 13:56:59 UTC

[jira] Commented: (HADOOP-5062) Namenode clients should recover from connection or Namenode restarts

    [ https://issues.apache.org/jira/browse/HADOOP-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12664509#action_12664509 ] 

Steve Loughran commented on HADOOP-5062:
----------------------------------------

OK, first item, do you want this to be transparent - the API does all the failure handling and restart, or do you want it explicit. 

For anyone who argues in favour of "transparent", I would point them at a a console full of "NFS server not responding still trying" messages, to show that transparency removes flexibility. 

> Namenode clients should recover from connection or Namenode restarts
> --------------------------------------------------------------------
>
>                 Key: HADOOP-5062
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5062
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>
> This Jira discusses the client side recovery from namenode restarts, fail overs and network connectivity issues. This does not address Namenode high availability and tracks only the client side recovery.

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