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] Resolved: (HADOOP-75) dfs should check full file availability only at close
Date Tue, 30 May 2006 23:02:30 GMT
     [ http://issues.apache.org/jira/browse/HADOOP-75?page=all ]
Doug Cutting resolved HADOOP-75:

    Resolution: Fixed
     Assign To: Milind Bhandarkar  (was: Konstantin Shvachko)

I just committed this.  Thanks, Milind!

> 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: Milind Bhandarkar
>     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:
For more information on JIRA, see:

View raw message