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 920C7DCDD for ; Fri, 19 Oct 2012 16:12:18 +0000 (UTC) Received: (qmail 75491 invoked by uid 500); 19 Oct 2012 16:12:16 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 75265 invoked by uid 500); 19 Oct 2012 16:12:16 -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 75232 invoked by uid 99); 19 Oct 2012 16:12:15 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Oct 2012 16:12:15 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jdcryans@gmail.com designates 209.85.212.41 as permitted sender) Received: from [209.85.212.41] (HELO mail-vb0-f41.google.com) (209.85.212.41) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Oct 2012 16:12:11 +0000 Received: by mail-vb0-f41.google.com with SMTP id v13so833998vbk.14 for ; Fri, 19 Oct 2012 09:11:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=n1v3/UmsCqrhCtFHyuKeANsGPWWFCNI0m6To+zw+xxk=; b=qC0uniqd3Uj/Yh2tIgOW3e2PUYCcqRV7/PLsDDzkHTUX0Xc7WUwHwUO0uAsdxii5i5 RhqF5UXCJ0qxr2u9+9iwVLQcsGIhjPM7hV8/FHI6Go/LMfsPaR572wYdOxyIrxtu4Ri9 7wOAZRxYt0bcusqUU1pJ1dWlQT3G9e2XIgKlhWDnXzl07a8LIUXzS0rEueP06pcnopMb dz1Cu7/YTrg1/OZJ4Ei09PLgJB3vUk6ueVBt8ycR5ZnmL5Xox/v4Lu+3tBBysGye6aCL f96nh8t/nHgyfYVzHpeUT3Mrea+KnmUQ4z/AAYgqWkArNFXfz3t/QKLoPEx263tN69Y9 n+Ug== MIME-Version: 1.0 Received: by 10.220.152.11 with SMTP id e11mr2187839vcw.61.1350663110311; Fri, 19 Oct 2012 09:11:50 -0700 (PDT) Sender: jdcryans@gmail.com Received: by 10.58.204.6 with HTTP; Fri, 19 Oct 2012 09:11:50 -0700 (PDT) In-Reply-To: References: <507fa10a.a750420a.3ec5.ffffb523SMTPIN_ADDED@mx.google.com> <507fcb76.4557420a.3f41.ffffbc56SMTPIN_ADDED@mx.google.com> Date: Fri, 19 Oct 2012 09:11:50 -0700 X-Google-Sender-Auth: TOQsR1ZAtciDd_zyFlhCvoulHUk Message-ID: Subject: Re: Checking major compaction From: Jean-Daniel Cryans To: user@hbase.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org You could just disable then enable the table. J-D On Fri, Oct 19, 2012 at 9:10 AM, kiran wrote: > Kevin, > > Thanks for your reply, > > can restarting region servers help to kill the already existing compaction > processes in region servers.. > > Thanks > Kiran > > On Fri, Oct 19, 2012 at 9:16 PM, Kevin O'dell wrote: > >> Kiran, >> >> I don't believe you can. If you have a sane region count/region size it >> should be over soon. >> >> On Fri, Oct 19, 2012 at 11:37 AM, kiran >> wrote: >> >> > Hi all, >> > >> > I mistakenly execution major compaction on the entire table instead of >> > region by region. It is causing so much delay in the write performance, >> > also on the disk and networkI/O. How can i stop major compaction now ? >> > >> > Thanks >> > Kiran >> > >> > On Thu, Oct 18, 2012 at 2:55 PM, Ramkrishna.S.Vasudevan < >> > ramkrishna.vasudevan@huawei.com> wrote: >> > >> > > >A simple test would be to just right some 10 rows >> > > I meant to say write some 10 rows.(not right) >> > > >> > > Regards >> > > Ram >> > > >> > > > -----Original Message----- >> > > > From: Ramkrishna.S.Vasudevan [mailto:ramkrishna.vasudevan@huawei.com >> ] >> > > > Sent: Thursday, October 18, 2012 2:05 PM >> > > > To: user@hbase.apache.org >> > > > Subject: RE: Checking major compaction >> > > > >> > > > Hi >> > > > >> > > > Yes Kiran you can go thro the logs also. >> > > > >> > > > You will see some logs like >> > > > 'Start major compaction for .............. >> > > > 'Compacting file ................ >> > > > 'Compacting file ................ >> > > > And finally 'Completed major/minor compaction.....' >> > > > >> > > > I just don have some exact logs with me right now. But you can see >> log >> > > > msgs >> > > > but all comes in debug mode. So ensure you enable debug mode for >> your >> > > > logs. >> > > > >> > > > A simple test would be to just right some 10 rows. In between do >> some 4 >> > > > to 5 >> > > > flushes. >> > > > >> > > > Just give major_compact(tableName) from the shell. You can see the >> > > > logs. >> > > > :) >> > > > >> > > > Regards >> > > > Ram >> > > > >> > > > > -----Original Message----- >> > > > > From: kiran [mailto:kiran.sarvabhotla@gmail.com] >> > > > > Sent: Thursday, October 18, 2012 12:03 PM >> > > > > To: user@hbase.apache.org >> > > > > Subject: Re: Checking major compaction >> > > > > >> > > > > Thanks ram, >> > > > > >> > > > > Is there a way can I check it through region server logs. If it is >> > > > > possible >> > > > > what are the statements that I need to look for ?? >> > > > > >> > > > > Thanks >> > > > > Kiran >> > > > > >> > > > > On Thu, Oct 18, 2012 at 11:55 AM, Ramkrishna.S.Vasudevan < >> > > > > ramkrishna.vasudevan@huawei.com> wrote: >> > > > > >> > > > > > HBASE-6033 does the work that you ask for. It is currently in >> > > > Trunk >> > > > > > version >> > > > > > of HBase. >> > > > > > >> > > > > > Regards >> > > > > > Ram >> > > > > > >> > > > > > > -----Original Message----- >> > > > > > > From: kiran [mailto:kiran.sarvabhotla@gmail.com] >> > > > > > > Sent: Thursday, October 18, 2012 11:43 AM >> > > > > > > To: user@hbase.apache.org >> > > > > > > Subject: Checking major compaction >> > > > > > > >> > > > > > > Hi all, >> > > > > > > >> > > > > > > Is there a way to check if major compaction is running or not >> on >> > > > a >> > > > > > > table. >> > > > > > > >> > > > > > > -- >> > > > > > > Thank you >> > > > > > > Kiran Sarvabhotla >> > > > > > > >> > > > > > > -----Even a correct decision is wrong when it is taken late >> > > > > > >> > > > > > >> > > > > >> > > > > >> > > > > -- >> > > > > Thank you >> > > > > Kiran Sarvabhotla >> > > > > >> > > > > -----Even a correct decision is wrong when it is taken late >> > > >> > > >> > >> > >> > -- >> > Thank you >> > Kiran Sarvabhotla >> > >> > -----Even a correct decision is wrong when it is taken late >> > >> >> >> >> -- >> Kevin O'Dell >> Customer Operations Engineer, Cloudera >> > > > > -- > Thank you > Kiran Sarvabhotla > > -----Even a correct decision is wrong when it is taken late