Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D734611932 for ; Mon, 14 Jul 2014 07:30:05 +0000 (UTC) Received: (qmail 40166 invoked by uid 500); 14 Jul 2014 07:30:04 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 40099 invoked by uid 500); 14 Jul 2014 07:30:04 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 40086 invoked by uid 99); 14 Jul 2014 07:30:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Jul 2014 07:30:03 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,SPF_SOFTFAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: softfail (athena.apache.org: transitioning domain of liyuming05@gmail.com does not designate 216.139.236.26 as permitted sender) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Jul 2014 07:29:59 +0000 Received: from ben.nabble.com ([192.168.236.152]) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1X6ahe-0000Hq-Sm for user@hbase.apache.org; Mon, 14 Jul 2014 00:29:38 -0700 Date: Mon, 14 Jul 2014 00:29:38 -0700 (PDT) From: vito To: user@hbase.apache.org Message-ID: <1405322978878-4061317.post@n3.nabble.com> In-Reply-To: References: <1405310247598-4061302.post@n3.nabble.com> <1405317927059-4061313.post@n3.nabble.com> Subject: Re: Will compaction block memstore flush to disk MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org >But if the number number of store files are beyond hbase.hstore.blockingStoreFiles, updates are blocked. Updates are blocked for period hbase.hstore.blockingWaitTime? or Updates can't be put into memstore? My understanding is the former. Certainly, updates can also be blocked by some memstore threshold, eg., hbase.regionserver.global.memstore.upperLimit or hbase.hregion.memstore.block.multiplier. Thanks. -- View this message in context: http://apache-hbase.679495.n3.nabble.com/Will-compaction-block-memstore-flush-to-disk-tp4061302p4061317.html Sent from the HBase User mailing list archive at Nabble.com.