[
https://issues.apache.org/jira/browse/HBASE-5954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13474886#comment-13474886
]
Luke Lu commented on HBASE-5954:
--------------------------------
bq. hsync is still better (even when it is not on the synchronous path, so
there's a little gap where a client was told that everything is on disk when in
fact it isn't).
No. It (hsync) is worse in the sense that there will be data loss (i.e.,
inconsistency: acked writes missing) if people bounce hdfs, while hbase is
still writing. Bouncing hdfs happens much more often in practice than actual
machine/pdu failures. To put it more strongly, hsync in the current hadoop 2 is
semantically wrong.
> 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
