hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1762) Namenode does not need to store storageID and datanodeID persistently
Date Tue, 18 Sep 2007 23:12:46 GMT

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

Hudson commented on HADOOP-1762:
--------------------------------

Integrated in Hadoop-Nightly #241 (See [http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Nightly/241/])

> 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
>             Fix For: 0.15.0
>
>         Attachments: HADOOP-1762-Opt2.patch, HADOOP-1762-Opt2.patch, HADOOP-1762-Opt2.patch,
HADOOP-1762-Opt2.patch, HADOOP-1762-Opt2.patch, HADOOP-1762-Opt2.patch, HADOOP-1762.patch,
HADOOP-1762.patch
>
>
> 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