hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raghu Angadi (JIRA)" <j...@apache.org>
Subject [jira] Created: (HADOOP-1762) Namenode does not need to store storageID and datanodeID persistently
Date Wed, 22 Aug 2007 22:20:30 GMT
Namenode does not need to store storageID and datanodeID persistently
---------------------------------------------------------------------

                 Key: HADOOP-1762
                 URL: https://issues.apache.org/jira/browse/HADOOP-1762
             Project: Hadoop
          Issue Type: Improvement
          Components: dfs
    Affects Versions: 0.14.0
            Reporter: Raghu Angadi
            Assignee: Raghu Angadi



Currently Namenode stores all the storage-ids it generates since the beginning (since last
format). It allocates a new storageID everytime a new datanode comes online. It also stores
all the known datanode ids since the beginning. 

It would be better if Namenode did not have to keep track of these. I will describe a proposal
in the next comment. 

This has implecations regd how Namenode helps administrators identify 'dead datanodes' etc.
These issues are addressed in HADOOP-1138.

-- 
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