You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Vikas Vishwakarma (JIRA)" <ji...@apache.org> on 2017/10/17 09:27:00 UTC

[jira] [Created] (HBASE-19024) provide a configurable option to hsync WAL edits to the disk for better durability

Vikas Vishwakarma created HBASE-19024:
-----------------------------------------

             Summary: provide a configurable option to hsync WAL edits to the disk for better durability
                 Key: HBASE-19024
                 URL: https://issues.apache.org/jira/browse/HBASE-19024
             Project: HBase
          Issue Type: Improvement
         Environment: 

            Reporter: Vikas Vishwakarma


At present we do not have an option to hsync WAL edits to the disk for better durability. In our local tests we see 10-15% latency impact of using hsync instead of hflush which is not very high.  
We should have a configurable option to hysnc WAL edits instead of just sync/hflush which will call the corresponding API on the hadoop side. Currently HBase handles both SYNC_WAL and FSYNC_WAL as the same calling FSDataOutputStream sync/hflush on the hadoop side. This can be modified to let FSYNC_WAL call hsync on the hadoop side instead of sync/hflush. We can keep the default value to sync as the current behavior and hsync can be enabled based on explicit configuration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)