Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E8B0510A46 for ; Mon, 29 Jul 2013 00:51:26 +0000 (UTC) Received: (qmail 92180 invoked by uid 500); 29 Jul 2013 00:51:26 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 92124 invoked by uid 500); 29 Jul 2013 00:51:26 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 92115 invoked by uid 99); 29 Jul 2013 00:51:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Jul 2013 00:51:26 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: error (athena.apache.org: local policy) Received: from [209.85.220.171] (HELO mail-vc0-f171.google.com) (209.85.220.171) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Jul 2013 00:51:22 +0000 Received: by mail-vc0-f171.google.com with SMTP id ij15so1691193vcb.16 for ; Sun, 28 Jul 2013 17:50:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:x-gm-message-state; bh=33UIVKukiQN+MQarjLfX1w+a+EYKRdz7B3Ao9bkeDFQ=; b=hv5BneJIod2Yts5Q7hpCtel4/+9PxChBFmwUUHmeqPZPqffT6srDR0C85lIoVqjhdQ hkMzq1S33MFwEe+npv2eYuXteOUpqtWGkQK8/49WXYe0YEL1RJ/nqtjcHbLdkacFg9Vl 7g5TVLdqonpzHQq7YzWsyCa9Mx3b3nkYdGfWA5brdIqPahswdlzq2Wn1q4lv1ZhC56+6 6Mb++/7F9WmYdqBVUA7JleDD5beStOvul3KS13RgoP6M/s2XxP64odL2OoW8PBQW8wDI zOtH/otPedp2AoFT/Wboug32IBbYQyyanR77H08ghWsTRZ6JflFC+gB1ur0qYNOJpVH5 Aw2w== X-Received: by 10.220.111.4 with SMTP id q4mr128293vcp.46.1375059040659; Sun, 28 Jul 2013 17:50:40 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.68.81 with HTTP; Sun, 28 Jul 2013 17:50:20 -0700 (PDT) In-Reply-To: References: From: Jean-Marc Spaggiari Date: Sun, 28 Jul 2013 20:50:20 -0400 Message-ID: Subject: Re: MAX_FILESIZE and hbase.hregion.max.filesize are both 10Gb To: dev@hbase.apache.org Content-Type: multipart/alternative; boundary=047d7b343b3aa9fbfd04e29be1a4 X-Gm-Message-State: ALoCoQntoRPkOrYSqjDYvoFtEQTY80u0Uo6JBxfzlehRPBgsXNb4RAA32C/xii2eQ0u84pWQWJme X-Virus-Checked: Checked by ClamAV on apache.org --047d7b343b3aa9fbfd04e29be1a4 Content-Type: text/plain; charset=UTF-8 "Yes it works, of course." It's not working for me ;) so was not sure. It's normal to have regions under the half of the MAX_FILESIZE. When a regions is more than MAX_FILESIZE it's splitted in 2. So one can be more, and the other one can be less. I will say, average 5GB will have been a good value, but even 3.6 is still not so bad. Have you pre-splitted the regions initially? Is it possible that you have not-used pre-splitted regions? You can you Hannibal to have a quick view of what the sizes are JM 2013/7/28 Vladimir Rodionov > The final stats: > > Total HDFS size - 376GB > #regions: 109 - avg. region size ~ 3.6GB > > Something is wrong here. I expected fewer regions. The regions get split > at sizes much lower than > hbase.hregion.max.filesize and/or MAX_FILESIZE. > > Best regards, > Vladimir Rodionov > Principal Platform Engineer > Carrier IQ, www.carrieriq.com > e-mail: vrodionov@carrieriq.com > > ________________________________________ > From: Vladimir Rodionov > Sent: Sunday, July 28, 2013 3:35 PM > To: dev@hbase.apache.org > Subject: RE: MAX_FILESIZE and hbase.hregion.max.filesize are both 10Gb > > Yes it works, of course. > > Its in original post - ~ 10gB > > > hbase.hregion.max.filesize > 10737418240 > hbase-site.xml > > > > Best regards, > Vladimir Rodionov > Principal Platform Engineer > Carrier IQ, www.carrieriq.com > e-mail: vrodionov@carrieriq.com > > ________________________________________ > From: Jean-Marc Spaggiari [jean-marc@spaggiari.org] > Sent: Sunday, July 28, 2013 2:30 PM > To: dev@hbase.apache.org > Subject: Re: MAX_FILESIZE and hbase.hregion.max.filesize are both 10Gb > > Hi Vladimir, > > Is this link working for you? http://MASTERURL:60010/conf ? If yes, what > do > you have for hbase.hregion.max.filesize? To make sure the property below is > considerered. > > For the table config, did you get it from the webui? > > JM > > 2013/7/28 Vladimir Rodionov > > > but all regions keep getting split at 1Gb > > > > I have 71 regions and 70GB of data in 'usertable' despite the fact that: > > > > table config is: > > {NAME => 'usertable', DEFERRED_LOG_FLUSH => 'true', MAX_FILESIZE => > > '10000000000', FAMILIES => [{NAME => 'cf', BLOOMFILTER => 'ROWCOL', > > VERSIONS => '1', COMPRESSION => 'GZ'}]} > > > > and hbase-size.xml has the following config: > > > > > > hbase.hregion.max.filesize > > 10737418240 > > hbase-site.xml > > > > > > HBase 0.94.6 > > > > Best regards, > > Vladimir Rodionov > > Principal Platform Engineer > > Carrier IQ, www.carrieriq.com > > e-mail: vrodionov@carrieriq.com > > > > Confidentiality Notice: The information contained in this message, > > including any attachments hereto, may be confidential and is intended to > be > > read only by the individual or entity to whom this message is addressed. > If > > the reader of this message is not the intended recipient or an agent or > > designee of the intended recipient, please note that any review, use, > > disclosure or distribution of this message or its attachments, in any > form, > > is strictly prohibited. If you have received this message in error, > please > > immediately notify the sender and/or Notifications@carrieriq.com and > > delete or destroy any copy of this message and its attachments. > > > > Confidentiality Notice: The information contained in this message, > including any attachments hereto, may be confidential and is intended to be > read only by the individual or entity to whom this message is addressed. If > the reader of this message is not the intended recipient or an agent or > designee of the intended recipient, please note that any review, use, > disclosure or distribution of this message or its attachments, in any form, > is strictly prohibited. If you have received this message in error, please > immediately notify the sender and/or Notifications@carrieriq.com and > delete or destroy any copy of this message and its attachments. > --047d7b343b3aa9fbfd04e29be1a4--