Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 33AA4DF95 for ; Tue, 30 Oct 2012 21:26:15 +0000 (UTC) Received: (qmail 53576 invoked by uid 500); 30 Oct 2012 21:26:14 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 53541 invoked by uid 500); 30 Oct 2012 21:26:14 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 53482 invoked by uid 99); 30 Oct 2012 21:26:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Oct 2012 21:26:14 +0000 Date: Tue, 30 Oct 2012 21:26:14 +0000 (UTC) From: "Kannan Muthukkaruppan (JIRA)" To: issues@hbase.apache.org Message-ID: <259906829.46968.1351632374873.JavaMail.jiratomcat@arcas> In-Reply-To: <226235135.32880.1349987103246.JavaMail.jiratomcat@arcas> Subject: [jira] [Updated] (HBASE-6980) Parallel Flushing Of Memstores [89-fb] MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-6980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kannan Muthukkaruppan updated HBASE-6980: ----------------------------------------- Fix Version/s: 0.89-fb Status: Patch Available (was: Open) http://svn.apache.org/viewvc?view=revision&revision=1403627 > Parallel Flushing Of Memstores [89-fb] > -------------------------------------- > > Key: HBASE-6980 > URL: https://issues.apache.org/jira/browse/HBASE-6980 > Project: HBase > Issue Type: New Feature > Reporter: Kannan Muthukkaruppan > Assignee: Kannan Muthukkaruppan > Fix For: 0.89-fb > > > 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-6981). > * 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