[
https://issues.apache.org/jira/browse/HDFS-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl updated HDFS-3979:
--------------------------------
Attachment: hdfs-3979-v4.txt
Updated patch with Nicholas' suggestion.
I agree that the previous patch would have slowed all writes that reach the DN.
We can't distinguish between an hflush from the client and "normal" packet from
the client.
On the other hand this no longer deals with Luke's "kill -9" scenario (where a
cluster management tool would kill -9 datanodes in parallel), but in the end no
tool really should do that.
> 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, 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
