Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 8 Dec 2017 06:42:01 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13109928.1508232414000.415723.1512715321880@Atlassian.JIRA>
In-Reply-To: <JIRA.13109928.1508232414000@Atlassian.JIRA>
References: <JIRA.13109928.1508232414000@Atlassian.JIRA> <JIRA.13109928.1508232414563@jira-lw-us.apache.org>
Subject: [jira] [Updated] (HBASE-19024) provide a configurable option to
 hsync WAL edits to the disk for better durability
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 08 Dec 2017 06:42:08 -0000


     [ https://issues.apache.org/jira/browse/HBASE-19024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-19024:
--------------------------
    Priority: Critical  (was: Major)

> 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
>            Priority: Critical
>         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
(v6.4.14#64029)