[
https://issues.apache.org/jira/browse/HBASE-19024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16267547#comment-16267547
]
Hadoop QA commented on HBASE-19024:
-----------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} docker {color} | {color:red} 4m
42s{color} | {color:red} Docker failed to build yetus/hbase:f29f170. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-19024 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12899488/HBASE-19024.branch-1.2.005.patch
|
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/10048/console |
| Powered by | Apache Yetus 0.6.0 http://yetus.apache.org |
This message was automatically generated.
> 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
(v6.4.14#64029)
