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 84B03187D5 for ; Sun, 2 Aug 2015 13:54:28 +0000 (UTC) Received: (qmail 62942 invoked by uid 500); 2 Aug 2015 13:54:26 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 62857 invoked by uid 500); 2 Aug 2015 13:54:26 -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 62843 invoked by uid 99); 2 Aug 2015 13:54:26 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Aug 2015 13:54:26 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 98B0BC0099 for ; Sun, 2 Aug 2015 13:54:25 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.879 X-Spam-Level: ** X-Spam-Status: No, score=2.879 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id bOWRoePOyOGl for ; Sun, 2 Aug 2015 13:54:24 +0000 (UTC) Received: from mail-vk0-f46.google.com (mail-vk0-f46.google.com [209.85.213.46]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id 4920D20595 for ; Sun, 2 Aug 2015 13:54:24 +0000 (UTC) Received: by vkca124 with SMTP id a124so34525491vkc.1 for ; Sun, 02 Aug 2015 06:54:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=bjYYzNLBS3joimUnOVHtVfDxh8v8BUf7p4Lw3ZmTrQE=; b=bfOC0AnOaEVxJnZreMVH9MppawLkGUTHy7x7u7MRYO4lXPtvqy34IQ53icWEF5Rp2N Ebay8i5oUhQbB87d5AqvoRdZhwiC252VfcNnhNpL9HAj+X7AiizNhyWO3fdQ3ZQ+F2HQ ailzmebr8/XsBrrDJZ2mg5Fht4lkdZ/AJ2CfxKpVs3R4lWwB2n6plf70T07DulbgARKI x1d4IFMJzBKBVuSLGBNtJfgrESb4VqdwZnUNbLNe59g3EPBL+U3mJ2/UnILuy4kBjdCM TEuecxl4VTDvnXVxpbQhlZK8zH409Clj/CgHjybD1MOmMhidZQTZGR5POkIIPZELPEp9 oQjQ== MIME-Version: 1.0 X-Received: by 10.52.64.204 with SMTP id q12mr20115516vds.89.1438523657342; Sun, 02 Aug 2015 06:54:17 -0700 (PDT) Received: by 10.31.230.135 with HTTP; Sun, 2 Aug 2015 06:54:17 -0700 (PDT) In-Reply-To: References: Date: Sun, 2 Aug 2015 21:54:17 +0800 Message-ID: Subject: Re: How does HBase manage Memstore From: Chang Chen To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=20cf307ac7ab98d3c4051c5463b5 --20cf307ac7ab98d3c4051c5463b5 Content-Type: text/plain; charset=UTF-8 Hi Ted we are using 0.96, so no hbase.hregion.percolumnfamilyflush.size.lower.bound exists. Besides these options, hbase.regionserver.optionalcacheflushinterval is also related to flush memstore. Thanks Chang On Sat, Aug 1, 2015 at 5:11 PM, Ted Yu wrote: > Here're some other memstore related config parameters: > > hbase.regionserver.global.memstore.size > hbase.regionserver.global.memstore.size.lower.limit > hbase.hregion.preclose.flush.size > hbase.hregion.memstore.block.multiplier > > hbase.hregion.percolumnfamilyflush.size.lower.bound > > The last one is for per column family flush. > You can find their meaning in > either hbase-common/src/main/resources/hbase-default.xml or, in > http://hbase.apache.org/book.html > > FYI > > On Sat, Aug 1, 2015 at 1:14 AM, Chang Chen wrote: > > > Hi All > > > > How does HBase flush memstore besides the configuration in > > [hbase.hregion.memstore.flush.size]? I believe we set flush size to 64M, > > but I find many *small* memstore flush logs as below > > > > 2015-06-25 10:19:09,243 INFO > org.apache.hadoop.hbase.regionserver.HRegion: > > Finished memstore flush of ~69.8 K/71520, currentsize=0/0 for region > > > user_intent_exp,1696512044,1426251005088.448ddc0071414b6af5729e4476ea35e8. > > in 26ms, sequenceid=18149727777, compaction requested=true > > > > 2015-06-25 10:20:54,428 INFO > org.apache.hadoop.hbase.regionserver.HRegion: > > Finished memstore flush of ~6.9 K/7104, currentsize=0/0 for region > > user_intent_exp,472446392,1426251005088.8d6041bd68dd431f5840357a2fd8bce2. > > in 30ms, sequenceid=18149728414, compaction requested=false > > > > > > Is there any other configuration which can affect flush? Will > HTable.close > > cause it happen? > > > > Thanks > > Chang > > > --20cf307ac7ab98d3c4051c5463b5--