[ 
https://issues.apache.org/jira/browse/HBASE-5954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13474827#comment-13474827
 ] 

Lars Hofhansl commented on HBASE-5954:
--------------------------------------

Hi Luke,

you mean hflush in hadoop 2 less durable than hflush in hadoop 1. 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).

Filed HDFS-3979 (you know that :), just for the benefit of others reading 
here), which needs some testing to be committed.

Since the hsync code is only in hadoop 2.1.0+ we'd need a new shim here for 
that version (or reflect the sh*t out of it).

I'm still happy to commit this to 0.94.x.
                
> 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

Reply via email to