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 "Edward Yoon (JIRA)" <ji...@apache.org> on 2008/03/07 03:36:59 UTC

[jira] Commented: (HADOOP-993) Namenode does not need to store any data node info persistently.

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

Edward Yoon commented on HADOOP-993:
------------------------------------

>> "in case of a misconfiguration of a datanode, namenode can tell which datanode "should" have a certain storageid" - You might be right here. But from my understanding, we have never had exploited this particular feature on our kryptonite cluster till now. 

Is kryptonite a cluster patronized by yahoo employee ?

> Namenode does not need to store any data node info persistently.
> ----------------------------------------------------------------
>
>                 Key: HADOOP-993
>                 URL: https://issues.apache.org/jira/browse/HADOOP-993
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: dfs
>            Reporter: Raghu Angadi
>            Assignee: Sameer Paranjpye
>         Attachments: noDatanodesInFsimage.patch
>
>
> Namenode does not need to serialize datanode info. It will map datanode to storageID when datanode register.

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