[
https://issues.apache.org/jira/browse/HDFS-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492321#comment-13492321
]
Hudson commented on HDFS-3979:
------------------------------
Integrated in Hadoop-Hdfs-trunk #1219 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1219/])
HDFS-3979. For hsync, datanode should wait for the local sync to complete
before sending ack. Contributed by Lars Hofhansl (Revision 1406382)
Result = SUCCESS
szetszwo :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1406382
Files :
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/BlockReceiver.java
> Fix hsync semantics
> -------------------
>
> Key: HDFS-3979
> URL: https://issues.apache.org/jira/browse/HDFS-3979
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: data-node
> Affects Versions: 2.0.2-alpha
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Fix For: 2.0.3-alpha
>
> Attachments: hdfs-3979-sketch.txt, hdfs-3979-v2.txt,
> hdfs-3979-v3.txt, hdfs-3979-v4.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
