[
https://issues.apache.org/jira/browse/HBASE-5954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475114#comment-13475114
]
Lars Hofhansl commented on HBASE-5954:
--------------------------------------
I disagree, having the signal out for the DNs to sync durably to disk now (even
if they only do as soon as they get to it) is better than having an indefinite
amount in which the data on only in volatile memory (which is as good as we can
get with only hflush).
But let's not harp this point... We all agree that it needs to be fixed.
I could use some help testing HDFS-3979. I believe the pipeline tests cover the
failure scenarios (which are the same whether we flush/sync or not), the test
needed there is verifying that the fsync is on the synchronous path of the
client.
> 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
