hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4862) A spurious IOException log on DataNode is not completely removed
Date Thu, 29 Jan 2009 04:53:59 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-4862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668344#action_12668344

Hadoop QA commented on HADOOP-4862:

-1 overall.  Here are the results of testing the latest attachment 
  against trunk revision 738602.

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no tests are needed for this patch.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

    +1 findbugs.  The patch does not introduce any new Findbugs warnings.

    +1 Eclipse classpath. The patch retains Eclipse classpath integrity.

    +1 core tests.  The patch passed core unit tests.

    -1 contrib tests.  The patch failed contrib unit tests.

Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3770/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3770/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3770/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3770/console

This message is automatically generated.

> A spurious IOException log on DataNode is not completely removed
> ----------------------------------------------------------------
>                 Key: HADOOP-4862
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4862
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.18.2
>         Environment: Minor : HADOOP-3678 did not remove all the cases of spurious IOExceptions
logged by DataNode.
>            Reporter: Raghu Angadi
>            Assignee: Raghu Angadi
>            Priority: Blocker
>             Fix For: 0.19.1
>         Attachments: HADOOP-4862-branch-18.patch, HADOOP-4862.patch, HADOOP-4862.patch
> HADOOP-3678 fixes a spurious warning log in DataNode, in most cases. This log is still
possible in some cases.
> For e.g. The exception is still logged if the client closes the connection after DataNode
writes all the block data but before it writes final 4 bytes to indicate end of data.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message