[
https://issues.apache.org/jira/browse/HDFS-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12765666#action_12765666
]
Suresh Srinivas commented on HDFS-679:
--------------------------------------
# Update the comments in DFSClient.java to say {{If this was the first write
after reopening a file, *if* the above write filled up any partial chunk...}}
# BlockReceiver.receivePacket() - calculation of offsetInChecksum - you may
have intended to put parenthesis around an expression and not just onDiskLen.
# BlockReceiver.receivePacket() - is reading and checking pre-existing checksum
necessary? What is the impact of this on performance with hflush?
# TestFileAppend2.testAppendToPartialChunk - add brief description to the test
# TestFileAppend2.testAppendToPartialChunk - It would be good if the write
tests not only partial chunk as it does now, but also a write that completes a
previous partial chunk and then writes partial chunk after that.
> Block receiver unexpectedly throws an IOException complaining mismatched
> checksum
> ---------------------------------------------------------------------------------
>
> 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
>
>
> 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.
