You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Hairong Kuang (JIRA)" <ji...@apache.org> on 2009/10/20 19:17:59 UTC

[jira] Updated: (HDFS-679) Appending to a partial chunk incorrectly assumes the first packet fills up the partial chunk

     [ https://issues.apache.org/jira/browse/HDFS-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hairong Kuang updated HDFS-679:
-------------------------------

    Summary: Appending to a partial chunk incorrectly assumes the first packet fills up the partial chunk  (was: Block receiver unexpectedly throws an IOException complaining mismatched checksum)

> Appending to a partial chunk incorrectly assumes the first packet fills up the partial chunk
> --------------------------------------------------------------------------------------------
>
>                 Key: HDFS-679
>                 URL: https://issues.apache.org/jira/browse/HDFS-679
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 0.21.0
>            Reporter: Hairong Kuang
>            Assignee: Hairong Kuang
>             Fix For: 0.21.0
>
>         Attachments: appendToPartialChunk.patch, appendToPartialChunk1.patch
>
>
> When I run TestClientProtocolForPipelineRecovery, I always see that the block receiver throws IOException complaining about mismatched checksum when receiving the last data packet. It turns out the checksum of last packet was unexpectedly set to be zero.

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