hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4862) A spurious IOException log on DataNode is not completely removed
Date Mon, 16 Feb 2009 17:02:29 GMT

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

Hudson commented on HADOOP-4862:
--------------------------------

Integrated in Hadoop-trunk #756 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/756/])
    

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


Mime
View raw message