From user-return-44098-apmail-hbase-user-archive=hbase.apache.org@hbase.apache.org Mon Jul 14 10:46:21 2014 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 E747F11E7F for ; Mon, 14 Jul 2014 10:46:21 +0000 (UTC) Received: (qmail 52781 invoked by uid 500); 14 Jul 2014 10:46:20 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 52715 invoked by uid 500); 14 Jul 2014 10:46:20 -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 52704 invoked by uid 99); 14 Jul 2014 10:46:19 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Jul 2014 10:46:19 +0000 X-ASF-Spam-Status: No, hits=3.9 required=5.0 tests=HTML_IMAGE_ONLY_20,HTML_MESSAGE,HTML_SHORT_LINK_IMG_3,RCVD_IN_DNSWL_LOW,SPF_PASS,T_REMOTE_IMAGE,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of bharathv@cloudera.com designates 209.85.214.176 as permitted sender) Received: from [209.85.214.176] (HELO mail-ob0-f176.google.com) (209.85.214.176) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Jul 2014 10:46:18 +0000 Received: by mail-ob0-f176.google.com with SMTP id wo20so3923300obc.7 for ; Mon, 14 Jul 2014 03:45:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=B1fGMG9zR5cYg7QPFThQmN3dRH0SGHqx90d94U34JWI=; b=Q1G9giVHNDIY8ciF/7aZ41pwQi2qkVhmMA668tZ4gzH2eXdgNl5EBWlrs1vq0J5JPS tRoeBqZKCesPodDXhzyLhbig/jaz5/MLsieXcosOg5Xc35pPntSPv8d2Pv2z+r5iAIqi +jfDo5T/8brT50C4N2HVFGnMbZLSMxwCxcWH0uJhtJK5kQmWiNgWBHkpFFrRGdVhskdx P6S91B6RXR8KMutI2D8nhCcUFW+zv2W5RBy1RiaJYDggo3ttvfOcxzvU2q8yaY42Lfbo OOz84gvXwveaY4AvcsJqJQwzbor9qZRwU5aSLQbpYBjWVuz3zqxYdC5YaVuIodykrtd3 taFA== X-Gm-Message-State: ALoCoQkeh5ftQ8+3lMO9vP7o2E3vrA+cQ6P5oZCCfgjUWatLPnbo4FRrgKM1zW9t6Gb+Vill93+w X-Received: by 10.60.52.5 with SMTP id p5mr2683019oeo.55.1405334753031; Mon, 14 Jul 2014 03:45:53 -0700 (PDT) MIME-Version: 1.0 Received: by 10.76.105.243 with HTTP; Mon, 14 Jul 2014 03:45:32 -0700 (PDT) In-Reply-To: <1405322978878-4061317.post@n3.nabble.com> References: <1405310247598-4061302.post@n3.nabble.com> <1405317927059-4061313.post@n3.nabble.com> <1405322978878-4061317.post@n3.nabble.com> From: Bharath Vissapragada Date: Mon, 14 Jul 2014 16:15:32 +0530 Message-ID: Subject: Re: Will compaction block memstore flush to disk To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=001a11332c8ebec8ed04fe24fe41 X-Virus-Checked: Checked by ClamAV on apache.org --001a11332c8ebec8ed04fe24fe41 Content-Type: text/plain; charset=UTF-8 Your understanding is correct. They are blocked for blockingWaitTime. Also as you mentioned it makes sure that the memory is not overused by putting "lowerLimit" and "upperLimit" on the total memory usage. This is mainly for heavy write scenarios where compactions can't keep up with frequent flushes. On Mon, Jul 14, 2014 at 12:59 PM, vito wrote: > > >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. > -- Bharath Vissapragada --001a11332c8ebec8ed04fe24fe41--