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 3F6AAD88F for ; Mon, 19 Nov 2012 21:47:32 +0000 (UTC) Received: (qmail 11352 invoked by uid 500); 19 Nov 2012 21:47:30 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 11267 invoked by uid 500); 19 Nov 2012 21:47: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 11257 invoked by uid 99); 19 Nov 2012 21:47:30 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Nov 2012 21:47:30 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.223.169] (HELO mail-ie0-f169.google.com) (209.85.223.169) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Nov 2012 21:47:24 +0000 Received: by mail-ie0-f169.google.com with SMTP id 10so9415717ied.14 for ; Mon, 19 Nov 2012 13:47:03 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=nExG09dyav9Pz82xN1PwRQ3O5ki+o9rh9/lo1R2fmZs=; b=oB+EfPjTJbQJnyKqL2aryGiJSZUOlsG9vpYUJQBfoC6EL8BeZNsUgLKJA1g5CEirBv FtbZD9U3+x21oXaT2vta26JEZsynsE7AG/MoaR/+DPgd1s0HqDE5SKfrhRB6baSQFHG0 xPVMKNSY8DJiK1tJfpEgnMx2Kb7mZy2gJuVL9dtOviP3oxzUChDmYuEMUpczQFTdr/T0 xkKV2s6IppLtsSN5ttABbTV9xSRXiSCf5269gW9JlXK+QjJcrKH2boppQtXjGs+h5z4A ysdj/WSxR7v7YUE4SMNqScPHPenUmW0hazMvpIqvaqTkZGgv33/KCSC0CMK5w6e/Hq2l tqCw== MIME-Version: 1.0 Received: by 10.42.249.80 with SMTP id mj16mr5031097icb.53.1353361623216; Mon, 19 Nov 2012 13:47:03 -0800 (PST) Received: by 10.64.42.229 with HTTP; Mon, 19 Nov 2012 13:47:03 -0800 (PST) In-Reply-To: References: Date: Mon, 19 Nov 2012 16:47:03 -0500 Message-ID: Subject: Re: 2 differents hbase.hregion.max.filesize at the same time? From: Jean-Marc Spaggiari To: user@hbase.apache.org Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQmr1BoDynvrD4xwDBNRu/9VkEsTPk/erWjFDwB/o0qtcKdk7DIR0r4PzkcLDborXyaw17/f X-Virus-Checked: Checked by ClamAV on apache.org Ok. I ran minor and major compaction, and it has split the table. I now have many regions. That's perfect! I still think a MIN_REGIONS option might be usefull or somethink like EVENLY_SPLIT. But at least I can adjust my settings with MAX_FILESIZE. Thanks, JM 2012/11/19, Jean-Marc Spaggiari : > Hi Kevin, > > Thanks for the suggestion. > > I have disabled the table, setup the MAX_FILESIZE value and enabled the > table. > > I can see that in the UI: > > work_proposed {NAME => 'work_proposed', MAX_FILESIZE => '104857600', > FAMILIES => [{NAME => '@'}]} > > But there is still only one region into the table. > > 104857600 is 100MB > > And here are the files in hadoop: > hadoop@node3:~/hadoop-1.0.3$ bin/hadoop fs -ls > /hbase/work_proposed/daca55e25f5ce23b358851990bd9d6a5/@ > Found 2 items > -rw-r--r-- 3 hbase supergroup 1340467822 2012-11-19 16:06 > /hbase/work_proposed/daca55e25f5ce23b358851990bd9d6a5/@/157867160e684800946dd129900d3f77 > -rw-r--r-- 3 hbase supergroup 834894008 2012-11-19 16:06 > /hbase/work_proposed/daca55e25f5ce23b358851990bd9d6a5/@/72bb17a94dc946da8db5841a37463713 > > The smallest one is almost 800MB. > > Something which might be interesting also will be to have something > like "MIN_REGIONS" where you can setup a number of minimum regions you > want for this table, whithout any consideration of the side of the > file. The goal here is to make sure the table is spread over enought > servers to distribut the work when there is major MapReduce jobs > running... Here, I have a 800MB file, and 8 region servers. I will > setup the MIN_REGIONS value to 8 and let hbase make sure there is at > least 8 regions for this table.... > > JM > > 2012/11/19, Kevin O'dell : >> JM, >> >> You can go into the shell -> disable table -> alter table command and >> chance MAX_FILESIZE(I think that is what it is) this will set it at a per >> table basis. >> >> On Mon, Nov 19, 2012 at 4:29 AM, Jean-Marc Spaggiari < >> jean-marc@spaggiari.org> wrote: >> >>> Hi, >>> >>> I have a 400M lines table that I merged yesterday into a single >>> region. I have previously splitted it wrongly. So I would like HBase >>> to split it its way. >>> >>> The issue is that keys are very small in this table and the 400M table >>> is stored on a <10G HFile. >>> >>> I still can use the split option on the HTML interface, but I was >>> wondering if there was a way to tell to hbase that the max filesize >>> for this specific table is 1G, but remains 10G for the other tables? >>> >>> My goal is to split this table into at least 8 pieces. So worst case, >>> since I know the number of lines, I can "simply" look at x/8 lines, >>> note the key, and continue. Then do the split. But is there a more >>> "automatic" way to do it? >>> >>> Thanks, >>> >>> JM >>> >> >> >> >> -- >> Kevin O'Dell >> Customer Operations Engineer, Cloudera >> >