hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-334) Redesign the dfs namespace datastructures to be copy on write
Date Mon, 06 Nov 2006 22:52:40 GMT
    [ http://issues.apache.org/jira/browse/HADOOP-334?page=comments#action_12447570 ] 
            
Doug Cutting commented on HADOOP-334:
-------------------------------------

> we do not need to clone all the nodes from a node to its root, we could clone only the
node that is being modified

I wonder whether this optimization is worthwhile.  It makes things more stateful, for example,
we can't have two separate snapshots live at once.  However I don't know that we'll ever need
to...

> Redesign the dfs namespace datastructures to be copy on write
> -------------------------------------------------------------
>
>                 Key: HADOOP-334
>                 URL: http://issues.apache.org/jira/browse/HADOOP-334
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: dfs
>    Affects Versions: 0.4.0
>            Reporter: Owen O'Malley
>         Assigned To: Konstantin Shvachko
>
> The namespace datastructures should be copy on write so that the namespace does not need
to be completely locked down from user changes while the checkpoint is being made.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message