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 "Raghu Angadi (JIRA)" <ji...@apache.org> on 2007/09/04 21:04:45 UTC

[jira] Resolved: (HADOOP-989) Namenode does not need to use Block objects

     [ https://issues.apache.org/jira/browse/HADOOP-989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Raghu Angadi resolved HADOOP-989.
---------------------------------

    Resolution: Won't Fix

Consumed/Invalidated by HADOOP-1687.

> Namenode does not need to use Block objects
> -------------------------------------------
>
>                 Key: HADOOP-989
>                 URL: https://issues.apache.org/jira/browse/HADOOP-989
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: dfs
>            Reporter: Raghu Angadi
>            Assignee: Raghu Angadi
>
> Currently Block object has Block ID and Block length. There are various maps in Namenode that map from or to Block objects but its length is rarely used and essentially a nice-to-have member. We could track only BlockIds in Namenode and if length is required we could store it in rest of the block related data (see HADOOP 988). 
> This will reduce memory and will make block look ups faster. 

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