hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-993) Namenode does not need to store any data node info persistently.
Date Wed, 21 Mar 2007 22:30:32 GMT

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

dhruba borthakur commented on HADOOP-993:
-----------------------------------------

After some discussion and code research, it appears to me that there is no real reason to
remove storing the datanodes from the fsimage. At least the storageid of the datanode needs
to be persisted (as pointed out by Yoram). A related issue is that datanodes that are dead
for a *long* period of time still appears as "dead" datanodes in the UI. 

We could close out this issue (unless somebody raises any questions) and we could open a new
JIRA issue to discuss how best to remove long-gone datanodes from appearing in the UI.


> 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
>          Issue Type: Improvement
>          Components: dfs
>            Reporter: Raghu Angadi
>         Assigned To: 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.


Mime
View raw message