[
https://issues.apache.org/jira/browse/HBASE-5954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475491#comment-13475491
]
Kan Zhang commented on HBASE-5954:
----------------------------------
Hi Lars, I think you did misunderstand what I said, esp. on the part "... with
respect to the semantics they support." :) As you know, post HDFS-265 hflush
implements API3 and when hflush returns data is guaranteed to be in the DN
buffers on all replica nodes, which is what API3 promises and client can't
expect anything more than that by calling hflush. But client would expect data
to hit disk by calling hsync, which is not guaranteed to happen in the current
implementation. The expected semantics are simply different for hflush and
hsync.
> Allow proper fsync support for HBase
> ------------------------------------
>
> Key: HBASE-5954
> URL: https://issues.apache.org/jira/browse/HBASE-5954
> Project: HBase
> Issue Type: Improvement
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Fix For: 0.94.3, 0.96.0
>
> Attachments: 5954-trunk-hdfs-trunk.txt, 5954-trunk-hdfs-trunk-v2.txt,
> 5954-trunk-hdfs-trunk-v3.txt, 5954-trunk-hdfs-trunk-v4.txt,
> 5954-trunk-hdfs-trunk-v5.txt, 5954-trunk-hdfs-trunk-v6.txt, hbase-hdfs-744.txt
>
>
--
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
