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 "Tsz Wo (Nicholas), SZE (JIRA)" <ji...@apache.org> on 2008/12/05 02:20:44 UTC
[jira] Commented: (HADOOP-4778) Check for zero size block meta file
when updating a block.
[ https://issues.apache.org/jira/browse/HADOOP-4778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653579#action_12653579 ]
Tsz Wo (Nicholas), SZE commented on HADOOP-4778:
------------------------------------------------
{noformat}
[exec] -1 overall.
[exec] +1 @author. The patch does not contain any @author tags.
[exec] -1 tests included. The patch doesn't appear to include any new or modified tests.
[exec] Please justify why no tests are needed for this patch.
[exec] +1 javadoc. The javadoc tool did not generate any warning messages.
[exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings.
[exec] +1 findbugs. The patch does not introduce any new Findbugs warnings.
[exec] +1 Eclipse classpath. The patch retains Eclipse classpath integrity.
{noformat}
The change is trivial. No new tests added.
> Check for zero size block meta file when updating a block.
> ----------------------------------------------------------
>
> Key: HADOOP-4778
> URL: https://issues.apache.org/jira/browse/HADOOP-4778
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Reporter: Tsz Wo (Nicholas), SZE
> Assignee: Tsz Wo (Nicholas), SZE
> Priority: Blocker
> Fix For: 0.18.3
>
> Attachments: 4769_20081203.patch, 4778_20081204.patch
>
>
> In case of datanode running out of disk space, block meta files may be created with zero length. We should detect this obvious problem when updating a block.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.