hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-19024) provide a configurable option to hsync WAL edits to the disk for better durability
Date Mon, 27 Nov 2017 21:02:00 GMT

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

Hadoop QA commented on HBASE-19024:

(!) A patch to the testing environment has been detected. 
Re-executing against the patched versions to perform further tests. 
The console is at https://builds.apache.org/job/PreCommit-HBASE-Build/10048/console in case
of problems.

> 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
>          Components: wal
>         Environment: 
>            Reporter: Vikas Vishwakarma
>            Assignee: Harshal Jain
>         Attachments: HBASE-19024.branch-1.2.001.patch, HBASE-19024.branch-1.2.002.patch,
HBASE-19024.branch-1.2.003.patch, HBASE-19024.branch-1.2.004.patch, HBASE-19024.branch-1.2.005.patch,
branch-1.branch-1.patch, branch-1.v1.branch-1.patch, master.patch, master.v2.patch, master.v3.patch,
master.v5.patch, master.v5.patch, master.v6.patch, master.v9.patch
> 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

View raw message