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 "Doug Cutting (JIRA)" <ji...@apache.org> on 2006/03/10 23:35:38 UTC
[jira] Created: (HADOOP-75) dfs should check full file availability
only at close
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.1
Reporter: Doug Cutting
Priority: Minor
Fix For: 0.1
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
[jira] Commented: (HADOOP-75) dfs should check full file
availability only at close
Posted by "Sameer Paranjpye (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-75?page=comments#action_12413878 ]
Sameer Paranjpye commented on HADOOP-75:
----------------------------------------
Doug, can this be committed for the 0.3 release?
> 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
[jira] Resolved: (HADOOP-75) dfs should check full file
availability only at close
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (HADOOP-75) dfs should check full file availability
only at close
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-75?page=all ]
Doug Cutting closed HADOOP-75:
------------------------------
> 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.0
> 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
[jira] Updated: (HADOOP-75) dfs should check full file availability
only at close
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-75?page=all ]
Doug Cutting updated HADOOP-75:
-------------------------------
Fix Version: 0.3
(was: 0.2)
> 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
>
> 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
[jira] Assigned: (HADOOP-75) dfs should check full file
availability only at close
Posted by "Sameer Paranjpye (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-75?page=all ]
Sameer Paranjpye reassigned HADOOP-75:
--------------------------------------
Assign To: Konstantin Shvachko
> 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.1
> Reporter: Doug Cutting
> Assignee: Konstantin Shvachko
> Priority: Minor
> Fix For: 0.1
>
> 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
[jira] Updated: (HADOOP-75) dfs should check full file availability
only at close
Posted by "Milind Bhandarkar (JIRA)" <ji...@apache.org>.
[ 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
[jira] Updated: (HADOOP-75) dfs should check full file availability
only at close
Posted by "Sameer Paranjpye (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-75?page=all ]
Sameer Paranjpye updated HADOOP-75:
-----------------------------------
Fix Version: 0.2
(was: 0.1)
Version: 0.2
(was: 0.1)
> 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.2
>
> 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