You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Milind Bhandarkar (JIRA)" <ji...@apache.org> on 2006/05/13 00:36:10 UTC

[jira] Updated: (HADOOP-75) dfs should check full file availability only at close

     [ http://issues.apache.org/jira/browse/HADOOP-75?page=all ]

Milind Bhandarkar updated HADOOP-75:
------------------------------------

    Attachment: hadoop-75.patch

Added a patch that removes that check (whether the previous blocks have been replicated or not) after adding every block to the file in construction. Now it checks that all file blocks have been replicated only at close of a file.

> dfs should check full file availability only at close
> -----------------------------------------------------
>
>          Key: HADOOP-75
>          URL: http://issues.apache.org/jira/browse/HADOOP-75
>      Project: Hadoop
>         Type: Improvement

>   Components: dfs
>     Versions: 0.2
>     Reporter: Doug Cutting
>     Assignee: Konstantin Shvachko
>     Priority: Minor
>      Fix For: 0.3
>  Attachments: hadoop-75.patch
>
> Currently it appears that dfs checks that the namenode knows about all blocks in a file as each block is written.  It would be more efficient to only check that all blocks are stored somewhere when the file is closed.

-- 
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