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 CC594DE33 for ; Wed, 13 Mar 2013 04:08:05 +0000 (UTC) Received: (qmail 66997 invoked by uid 500); 13 Mar 2013 04:08:03 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 66937 invoked by uid 500); 13 Mar 2013 04:08:03 -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 66901 invoked by uid 99); 13 Mar 2013 04:08:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Mar 2013 04:08:01 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of saint.ack@gmail.com designates 209.85.214.46 as permitted sender) Received: from [209.85.214.46] (HELO mail-bk0-f46.google.com) (209.85.214.46) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Mar 2013 04:07:57 +0000 Received: by mail-bk0-f46.google.com with SMTP id j5so236953bkw.19 for ; Tue, 12 Mar 2013 21:07:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=KmozOH4aif4vG7ZCiyQaZZmqcGhH9Wg1AIybH3+3Q5g=; b=M4GKAKWsVabndScHFPjVRZmKYhtMFAcOpjvDoTmsQU+1rQUEYJnFCOQ4G3czXukFMZ pUqlWUG1nVQwV8QXZpsLrValPxNduso2a9fu5qgx+ZIVsHtaGe0T15fj0PJYymNRV/Hi GB9FhtIGt1Op0K4pPt20gKClWKSsfGeSSvPIApK+4+C1i+hDm/K3EqxqtBvMbPqaqhPg e4cqDaQyDU102liLwJqQTGRnXXHYqR+EPUx53Wje1z5NjwQDHXQaCT77ngp+U+rKpCIO 75JE0V3S9lzT/ToXrdOWkBPN1wpQNdSaaHg8oCnqY9PNy/L4rlGH0hpU0x7XCLBEnbSw J8DQ== MIME-Version: 1.0 X-Received: by 10.204.244.135 with SMTP id lq7mr3007001bkb.138.1363147655817; Tue, 12 Mar 2013 21:07:35 -0700 (PDT) Sender: saint.ack@gmail.com Received: by 10.204.147.22 with HTTP; Tue, 12 Mar 2013 21:07:35 -0700 (PDT) In-Reply-To: <391D65D0EBFC9B4B95E117F72A360F1A1E7248@SHSMSX101.ccr.corp.intel.com> References: <391D65D0EBFC9B4B95E117F72A360F1A1E6A70@SHSMSX101.ccr.corp.intel.com> <391D65D0EBFC9B4B95E117F72A360F1A1E7248@SHSMSX101.ccr.corp.intel.com> Date: Tue, 12 Mar 2013 21:07:35 -0700 X-Google-Sender-Auth: jmWC-vZkLoxFUhh5P-DZDKkiy0M Message-ID: Subject: Re: Does a major compact flush memstore? From: Stack To: Hbase-User Content-Type: multipart/alternative; boundary=f46d041c46aacd6dff04d7c68b9a X-Virus-Checked: Checked by ClamAV on apache.org --f46d041c46aacd6dff04d7c68b9a Content-Type: text/plain; charset=UTF-8 Raymond: Major compaction does not first flush. Should it or should it be an option? St.Ack On Tue, Mar 12, 2013 at 6:46 PM, Liu, Raymond wrote: > I tried both hbase shell's major_compact cmd and java api > HBaseAdmin.majorCompact() on table name. > They don't flush the memstore on to disk, compact cmd seems not doing that > too. > > I hadn't read enough related code, While I am wondering, is that because > there are size threshold before a memstore is flushed? Then a user invoked > compact don't force to flush it? > > Best Regards, > Raymond Liu > > > > > Did you try from java api? If flush does not happen we may need to fix > it. > > > > Regards > > RAm > > > > On Tue, Mar 12, 2013 at 1:04 PM, Liu, Raymond > > wrote: > > > > > It seems to me that a major_compact table command from hbase shell do > > > not fush memstore? When I done with major compact, still some data in > > > memstore and will be flush out to disk when I shut down hbase cluster. > > > > > > Best Regards, > > > Raymond Liu > > > > > > > --f46d041c46aacd6dff04d7c68b9a--