hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elliott Clark (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14540) Write Ahead Log Batching Optimization
Date Fri, 02 Oct 2015 16:27:27 GMT

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

Elliott Clark commented on HBASE-14540:
---------------------------------------

I think something like this could really add throughput for people who have an olap workload,
so we should totally try this out and then make it an option. Just allow online workloads
to use something else.

> Write Ahead Log Batching Optimization
> -------------------------------------
>
>                 Key: HBASE-14540
>                 URL: https://issues.apache.org/jira/browse/HBASE-14540
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: John Leach
>         Attachments: HBaseWALBlockingWaitStrategy.java
>
>
> The new write ahead log mechanism seems to batch too few mutations when running inside
the disruptor.  As we scaled our load up (many threads with small writes), we saw the number
of hdfs sync operations grow in concert with the number of writes.  Generally, one would expect
the size of the batches to grow but the number of actual sync operations to settle. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message