Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 15 Jul 2014 21:51:08 +0000 (UTC)
From: "Tsz Wo Nicholas Sze (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12671591.1380638797900.48966.1405461068221@arcas>
In-Reply-To: <JIRA.12671591.1380638797900@arcas>
References: <JIRA.12671591.1380638797900@arcas>
Subject: [jira] [Assigned] (HDFS-5284) Flatten INode hierarchy
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Tsz Wo Nicholas Sze reassigned HDFS-5284:
-----------------------------------------

    Assignee: Jing Zhao  (was: Tsz Wo Nicholas Sze)

> Flatten INode hierarchy
> -----------------------
>
>                 Key: HDFS-5284
>                 URL: https://issues.apache.org/jira/browse/HDFS-5284
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>    Affects Versions: 2.4.0
>            Reporter: Tsz Wo Nicholas Sze
>            Assignee: Jing Zhao
>
> Currently, we have a complicated inode hierarchy for representing different states of a file or a directory.  For example,  when a file is being created, it is represented by an INodeFileUnderConstruction.  When a file is being closed, the inode is replaced by an INodeFile.  If it is reopened for append, the inode is replaced again by an INodeFileUnderConstruction.  This JIRA is to flatten the inode hierarchy.  We may also improve the performance by eliminating the inode replacement in runtime.


--
This message was sent by Atlassian JIRA
(v6.2#6252)