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

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/12684104/HDFS-7437.002.patch
  against trunk revision c1f2bb2.

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 7 new 
or modified test files.

    {color:red}-1 javac{color:red}.  The patch appears to cause the build to 
fail.

Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/8866//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, 
> HDFS-7437.002.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)

Reply via email to