hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HDFS-1346) DFSClient receives out of order packet ack
Date Thu, 19 Aug 2010 01:28:18 GMT

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

Todd Lipcon updated HDFS-1346:

    Attachment: blockrecv-diff.txt

I'm noticing that the HDFS-101 implementation we've been running with is a bit different than
what made it into the branch-0.20-append, and I don't think susceptible to the issue. Attaching
a diff of our BlockReceiver.java against the branch-20-append one - ignore the bit at the
end with checkDiskError, etc - that's from another patch.

I think the relevent diff chunk here is the first - we detect a HEART_BEAT seqno immediately
and "continue" around the loop in that case. Is this a cleaner fix than the local variable?

> DFSClient receives out of order packet ack
> ------------------------------------------
>                 Key: HDFS-1346
>                 URL: https://issues.apache.org/jira/browse/HDFS-1346
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: data-node, hdfs client
>    Affects Versions: 0.20-append
>            Reporter: Hairong Kuang
>            Assignee: Hairong Kuang
>             Fix For: 0.20-append
>         Attachments: blockrecv-diff.txt, outOfOrder.patch
> When running 0.20 patched with HDFS-101, we sometimes see an error as follow:
> WARN hdfs.DFSClient: DFSOutputStream ResponseProcessor exception for block blk_-2871223654872350746_21421120java.io.IOException:
Responseprocessor: Expecting seq
> no for block blk_-2871223654872350746_21421120 10280 but received 10281
> at org.apache.hadoop.hdfs.DFSClient$DFSOutputStream$ResponseProcessor.run(DFSClient.java:2570)
> This indicates that DFS client expects an ack for packet N, but receives an ack for packet

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

View raw message