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-8248) Store INodeId instead of the INodeFile object in BlockInfoContiguous
Date Mon, 27 Apr 2015 21:39:39 GMT

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

Hadoop QA commented on HDFS-8248:

(!) The patch artifact directory on has been removed! 
This is a fatal error for test-patch.sh.  Aborting. 
Jenkins (node H4) information at https://builds.apache.org/job/PreCommit-HDFS-Build/10413/
may provide some hints.

> Store INodeId instead of the INodeFile object in BlockInfoContiguous
> --------------------------------------------------------------------
>                 Key: HDFS-8248
>                 URL: https://issues.apache.org/jira/browse/HDFS-8248
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Haohui Mai
>            Assignee: Haohui Mai
>         Attachments: HDFS-8248.000.patch, HDFS-8248.001.patch
> Currently the namespace and the block manager are tightly coupled together. There are
two couplings in terms of implementation:
> 1. The {{BlockInfoContiguous}} stores a reference of the {{INodeFile}} that owns the
block, so that the block manager can look up the corresponding file when replicating blocks,
recovering from pipeline failures, etc.
> 1. The {{INodeFile}} stores {{BlockInfoContiguous}} objects that the file owns.
> Decoupling the namespace and the block manager allows the BM to be separated out from
the Java heap or even as a standalone process. This jira proposes to remove the first coupling
by storing the id of the inode instead of the object reference of {{INodeFile}} in the {{BlockInfoContiguous}}

This message was sent by Atlassian JIRA

View raw message