[
https://issues.apache.org/jira/browse/HBASE-6980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kannan Muthukkaruppan updated HBASE-6980:
-----------------------------------------
Description:
For write dominated workloads, single threaded memstore flushing is an
unnecessary bottleneck. With a single flusher thread, we are basically not
setup to take advantage of the aggregate throughput that multi-disk nodes
provide.
* For puts with WAL enabled, the bottleneck is more likely the "single" WAL per
region server. So this particular fix may not buy as much unless we unlock that
bottleneck with multiple commit logs per region server. (Topic for a separate
JIRA-- HBASE-6980).
* But for puts with WAL disabled (e.g., when using HBASE-5783 style fast bulk
imports), we should be able to support much better ingest rates with parallel
flushing of memstores.
was:
For write dominated workloads, single threaded memstore flushing is an
unnecessary bottleneck. With a single flusher thread, we are basically not
setup to take advantage of the aggregate throughput that multi-disk nodes
provide.
* For puts with WAL enabled, the bottleneck is more likely the "single" WAL per
region server. So this particular fix may not buy as much unless we unlock that
bottleneck with multiple commit logs per region server. [Topic for a separate
JIRA.]
* But for puts with WAL disabled (e.g., when using HBASE-5783 style fast bulk
imports), we should be able to support much better ingest rates with parallel
flushing of memstores.
> Parallel Flushing Of Memstores
> ------------------------------
>
> Key: HBASE-6980
> URL: https://issues.apache.org/jira/browse/HBASE-6980
> Project: HBase
> Issue Type: New Feature
> Reporter: Kannan Muthukkaruppan
> Assignee: Kannan Muthukkaruppan
>
> For write dominated workloads, single threaded memstore flushing is an
> unnecessary bottleneck. With a single flusher thread, we are basically not
> setup to take advantage of the aggregate throughput that multi-disk nodes
> provide.
> * For puts with WAL enabled, the bottleneck is more likely the "single" WAL
> per region server. So this particular fix may not buy as much unless we
> unlock that bottleneck with multiple commit logs per region server. (Topic
> for a separate JIRA-- HBASE-6980).
> * But for puts with WAL disabled (e.g., when using HBASE-5783 style fast bulk
> imports), we should be able to support much better ingest rates with parallel
> flushing of memstores.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
