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 9891BD67B for ; Mon, 4 Mar 2013 13:41:32 +0000 (UTC) Received: (qmail 75763 invoked by uid 500); 4 Mar 2013 13:41:30 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 75514 invoked by uid 500); 4 Mar 2013 13:41:30 -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 75490 invoked by uid 99); 4 Mar 2013 13:41:29 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Mar 2013 13:41:29 +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 (nike.apache.org: domain of samar.opensource@gmail.com designates 209.85.210.43 as permitted sender) Received: from [209.85.210.43] (HELO mail-da0-f43.google.com) (209.85.210.43) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Mar 2013 13:41:21 +0000 Received: by mail-da0-f43.google.com with SMTP id u36so2569226dak.30 for ; Mon, 04 Mar 2013 05:41:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type; bh=DA3WcRALyew+KZ9x0yfe2UlpiS91Dths5HzcBRIATYM=; b=drb9jek0a3WqgBkAwu2nKA1Qqgnvbb7YBgiseFxR1wp5l1wldkkodgXUBNXizneMxE rrZU47dOCUCQqk5bQr7r7yCmrfnU9aOduzNKE+qB/CA/hpO8/b+N5s3EVXNJZLxAlJOe W4YmegRzSJhYXhfHCcGtQy+gHZA3/FaqzOzsXwwkh+GJxjYI7a+2YKZFjSfW3mBxcBC9 qGgEANvFY7EU1gCnEUcbdYKMvdhGpfV1P4Tlr6hU6OJMHx1fvJqZz4hpCSi/k0UH1fQ2 1dswUvVfF8FZVsH1qIOK0OLzV9pczFG9B/ZI3ueaZPdmgNXxFlU3vTHPYOowN7L9DZTt yGGA== X-Received: by 10.68.134.233 with SMTP id pn9mr28434007pbb.90.1362404460651; Mon, 04 Mar 2013 05:41:00 -0800 (PST) Received: from r9_1fdxt.mkhoj.com (210-210-41-202.lan.sify.net. [210.210.41.202]) by mx.google.com with ESMTPS id pn9sm22366510pbb.22.2013.03.04.05.40.58 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 04 Mar 2013 05:41:00 -0800 (PST) Message-ID: <5134A467.4030700@gmail.com> Date: Mon, 04 Mar 2013 19:10:55 +0530 From: "samar.opensource" User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130216 Thunderbird/17.0.3 MIME-Version: 1.0 To: user@hbase.apache.org CC: Jean-Marc Spaggiari Subject: Re: Compaction time References: <513442E3.2050605@gmail.com> <51345404.4010909@gmail.com> In-Reply-To: Content-Type: multipart/alternative; boundary="------------040103060307050402090405" X-Virus-Checked: Checked by ClamAV on apache.org --------------040103060307050402090405 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Thanks Viral and Jean, Sounds like timing the compactions is the only options now. Is it ok we put a large number to *|hbase.hstore.blockingStoreFiles|* so that even if compaction happens, automatic or manual , blocking rarely happens. Is compaction time like 20-40 mins normal for a 2GB store . Regards, Samar On 04/03/13 6:20 PM, Jean-Marc Spaggiari wrote: > So can you simply do something like disabling automatic compactions, > and run small manual one after each light job? That way it might not > impact you heavy job with a big 40 minutes compactions since data will > almost alway be compacted correctly? You can even maybe keep the > automatic compaction to on if you do that since when you heavy job > will run, your data compaction will be almost totally done. > > JM > > 2013/3/4 samar.opensource : >> Hi Viral, >> The jobs dont run often. may be few times a day(10 ). But the problem is >> there are other application which are running other jobs which may not be as >> heavy but running compaction any time might block those jobs. >> so there is >> heavy jobs running less frequently >> and light jobs running more frequently >> >> Regards, >> Samar >> >> On 04/03/13 12:26 PM, Viral Bajaria wrote: >>> How often do you run those jobs ? Do they run periodically or are they >>> running all the time ? >>> >>> If you have a predictable periodic behavior, you could disable automatic >>> compaction and trigger it manually using a cron job (not the recommended >>> approach, AFAIK). Or you could set the compaction to trigger at a set time >>> of the day when you know your jobs are not running. >>> >>> -Viral >>> >>> On Sun, Mar 3, 2013 at 10:44 PM, samar.opensource < >>> samar.opensource@gmail.com> wrote: >>> >>>> Hi, >>>> We are running some high load jobs which are mostly writes. During >>>> these jobs, compaction is triggered which takes sometime as longs as >>>> 40mins >>>> to complete. This causes blocking (as others wait for compaction in the >>>> queue). Please suggest how much compaction time is reasonable for >>>> compacting 2Gb store files . And best way to avoid long blocking >>>> compactions. >>>> Using Cloudera hbase vesion 3u3. >>>> Regards, >>>> Samar >>>> --------------040103060307050402090405--