hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7437) Storing block ids instead of BlockInfo object in INodeFile
Date Wed, 26 Nov 2014 18:52:13 GMT

    [ https://issues.apache.org/jira/browse/HDFS-7437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14226641#comment-14226641
] 

Hadoop QA commented on HDFS-7437:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12683891/HDFS-7437.001.patch
  against trunk revision f5b1631.

    {color:red}-1 patch{color}.  Trunk compilation may be broken.

Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/8849//console

This message is automatically generated.

> Storing block ids instead of BlockInfo object in INodeFile
> ----------------------------------------------------------
>
>                 Key: HDFS-7437
>                 URL: https://issues.apache.org/jira/browse/HDFS-7437
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Haohui Mai
>            Assignee: Haohui Mai
>         Attachments: HDFS-7437.000.patch, HDFS-7437.001.patch
>
>
> Currently {{INodeFile}} stores the lists of blocks as references of {{BlockInfo}} instead
of the block ids. This creates implicit dependency between the namespace and the block manager.
> The dependency blocks several recent efforts, such as separating the block manager out
as a standalone service, moving block information off heap, and optimizing the memory usage
of block manager.
> This jira proposes to decouple the dependency by storing block ids instead of object
reference in {{INodeFile}} objects.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message