[
https://issues.apache.org/jira/browse/HDFS-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13465386#comment-13465386
]
Lars Hofhansl commented on HDFS-3979:
-------------------------------------
Should we simply do the enqueue at the end of receivePacket(), then?
So just to make sure: In the current code the seqno is already enqueued in the
beginning, so if there's an exception later in the code it won't have any
effect on the enqued seqno. The finally is just preserves this existing
behavior.
What happens when there is an exception and the seqno is never enqueued? (and
if that is OK, why is it not a problem now.)
> Fix hsync and hflush semantics.
> -------------------------------
>
> Key: HDFS-3979
> URL: https://issues.apache.org/jira/browse/HDFS-3979
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: data-node, hdfs client
> Affects Versions: 0.22.0, 0.23.0, 2.0.0-alpha
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Attachments: hdfs-3979-sketch.txt
>
>
> See discussion in HDFS-744. The actual sync/flush operation in BlockReceiver
> is not on a synchronous path from the DFSClient, hence it is possible that a
> DN loses data that it has already acknowledged as persisted to a client.
> Edit: Spelling.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
