Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 30 Jul 2012 06:09:36 +0000 (UTC)
From: "ramkrishna.s.vasudevan (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <1262918512.115330.1343628576746.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <839112812.109262.1343358875725.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (HBASE-6466) Enable multi-thread for memstore
 flush
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

ramkrishna.s.vasudevan commented on HBASE-6466:
-----------------------------------------------

@Chunhui
bq.(meaning that while one thread flushes, the others are blocking the inserts and not flushing)
The above is one of JD's comments.  Currently the patch tries to make more flushes concurrently.  So in startCacheFlush we will now be blocking the incoming writes more right?
As more flush threads will try getting the updatesLock.writeLock. I may be wrong here.  Pls correct me..Thanks..
                
> Enable multi-thread for memstore flush
> --------------------------------------
>
>                 Key: HBASE-6466
>                 URL: https://issues.apache.org/jira/browse/HBASE-6466
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: chunhui shen
>            Assignee: chunhui shen
>         Attachments: HBASE-6466.patch, HBASE-6466v2.patch, HBASE-6466v3.patch
>
>
> If the KV is large or Hlog is closed with high-pressure putting, we found memstore is often above the high water mark and block the putting.
> So should we enable multi-thread for Memstore Flush?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira