Return-Path: 
 <user-return-42637-apmail-hbase-user-archive=hbase.apache.org@hbase.apache.org>
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 7DAB711AFA
	for <apmail-hbase-user-archive@www.apache.org>;
 Wed,  9 Apr 2014 19:40:57 +0000 (UTC)
Received: (qmail 97087 invoked by uid 500); 9 Apr 2014 19:40:47 -0000
Delivered-To: apmail-hbase-user-archive@hbase.apache.org
Received: (qmail 96899 invoked by uid 500); 9 Apr 2014 19:40:46 -0000
Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@hbase.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@hbase.apache.org>
List-Post: <mailto:user@hbase.apache.org>
List-Id: <user.hbase.apache.org>
Reply-To: user@hbase.apache.org
Delivered-To: mailing list user@hbase.apache.org
Received: (qmail 96882 invoked by uid 99); 9 Apr 2014 19:40:45 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Apr 2014 19:40:45 +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: local policy includes SPF record at
 spf.trusted-forwarder.org)
Received: from [209.85.128.169] (HELO mail-ve0-f169.google.com)
 (209.85.128.169)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Apr 2014 19:40:40 +0000
Received: by mail-ve0-f169.google.com with SMTP id pa12so2536526veb.14
        for <user@hbase.apache.org>; Wed, 09 Apr 2014 12:40:18 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:mime-version:in-reply-to:references:from:date
         :message-id:subject:to:content-type;
        bh=7qe8zQWFMwvQ7glzB2rR5FprZs4zG9VmtMGmgLcjW4o=;
        b=mlyGgEsf6rdDq/TFEQHyo5ZwT8waQb8GK10eFCJoAHRS84mUG3UAvpXgUf4VXZtHBj
         tvr43sdUEw1PgWpxPvDWJ6q4JAEpL+zDCkv35SU2bZ3aaSJCsQBGqJThzD1WMS9Xa9o+
         NYw/SREyDMZltqz88HEaeSyMVrzNjiQ6LR4f0vKR/O7EV70Hgv87s17Lvr6/GwiI1rFa
         eLwJw3EdKdgiz0vfrOif9sa1E7mkO5OhSW2bp8iL446+EEUqngSQNEcTa/rpyve2h7na
         9J5Y0WN0gvZhnzU8m4b3iuRxfbM2jGL7c5DOlTWKdB/pLvjCaO/4OIYYL8hSpj/RTVc1
         KuSQ==
X-Gm-Message-State: 
 ALoCoQn0R3KfFzaSBqjryxrtvcJkPWC+epAAcWFKddXOt+jQtkSGD5ba9q/iODfIWxcDrXpu+xZE
X-Received: by 10.221.58.144 with SMTP id wk16mr2667440vcb.23.1397072418029;
 Wed, 09 Apr 2014 12:40:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.5.98 with HTTP; Wed, 9 Apr 2014 12:39:57 -0700 (PDT)
In-Reply-To: 
 <CAPQV63UtMnOL-XifoPiA_JD4vRryc8ZYCpB=YN_1uk5+T2r8CQ@mail.gmail.com>
References: 
 <CAPQV63UtMnOL-XifoPiA_JD4vRryc8ZYCpB=YN_1uk5+T2r8CQ@mail.gmail.com>
From: Jean-Marc Spaggiari <jean-marc@spaggiari.org>
Date: Wed, 9 Apr 2014 15:39:57 -0400
Message-ID: 
 <CAPQV63Us1VGO4w5ALN4ZdqVT0Xo75NvZ_mL1=E78EK40dNEmPw@mail.gmail.com>
Subject: Re: HBase 0.98.1 split policy change?
To: user <user@hbase.apache.org>
Content-Type: multipart/alternative; boundary=001a1133182c33d5a404f6a145ac
X-Virus-Checked: Checked by ClamAV on apache.org

--001a1133182c33d5a404f6a145ac
Content-Type: text/plain; charset=UTF-8

Ok. From the logs, I can clearly see that my settings are not getting use:

2014-04-09 15:35:03,737 DEBUG [MemStoreFlusher.0]
regionserver.IncreasingToUpperBoundRegionSplitPolicy: ShouldSplit because
info size=2242479890, sizeToCheck=2147483648, regionsWithCommonTable=2

I will try to figure why and report.

JM



2014-04-09 15:25 GMT-04:00 Jean-Marc Spaggiari <jean-marc@spaggiari.org>:

> Hi,
>
> I try to chance my HBase 0.98.1 split policy to be
> ConstantSizeRegionSplitPolicy so I have updated my hbase-site.xml do be
> this:
>
>   <property>
>     <name>hbase.regionserver.region.split.policy</name>
>
> <value>org.apache.hadoop.hbase.regionserver.ConstantSizeRegionSplitPolicy</value>
>   </property>
>
> Then on my table I have altered to get this where regions size should be
> 100GB:
> hbase(main):002:0> describe 'TestTable'
> DESCRIPTION
>
>  'TestTable', {TABLE_ATTRIBUTES => {MAX_FILESIZE => '1073741824000'},
> {NAME => 'info', DATA_BLOCK_ENCODING => 'NONE', BLOOMFILTER => 'ROW',
> REPLICATION_SCOPE => '0', COMPRESSION => 'NONE', VERSIONS => '1', TTL => '
> 2147483647', MIN_VERSIONS => '0', KEEP_DELETED_CELLS => 'false',
> BLOCKSIZE => '65536', IN_MEMORY => 'false', BLOCKCACHE =>
> 'true'}
>
> 1 row(s) in 0.2480 seconds
>
> However, I'm still getting multiple small regions with I try randomWrite
> into the table:
> hadoop@hbasetest1:~$ bin/hadoop fs -du -h /hbase/data/default/TestTable
> 14/04/09 15:08:13 WARN util.NativeCodeLoader: Unable to load native-hadoop
> library for your platform... using builtin-java classes where applicable
> 320    /hbase/data/default/TestTable/.tabledesc
> 0      /hbase/data/default/TestTable/.tmp
> 1.6 G  /hbase/data/default/TestTable/1ad732fefba8ab6080820fb235fd5180
> 2.0 G  /hbase/data/default/TestTable/585b3e11d64cabcff332a2e293a37fee
> 1.5 G  /hbase/data/default/TestTable/6e8c24a2cc03051bb8a0990e22b8ec21
> 1.5 G  /hbase/data/default/TestTable/73fc51f6d6d75e57be29a1f7d54ef1df
> 1.4 G  /hbase/data/default/TestTable/ac69f15956bf413805982439a05527fd
> 2.5 G  /hbase/data/default/TestTable/cfb60af42b92fd9c2abfab80306d257c
>
> With the split policy setting and the alter, I will have expected to have
> a single region of few GB and not multiple regions. I checked inthe WebUI
> for the config and I can see my splitpolicy entry. What did I missed? I
> checked the ConstantSizeRegionSplitPolicy in 0.98 and it uses MAX_FILESIZE
> from the table, and hbase.hregion.max.filesize which is not setup for me.
> Any idea?
>
> JM
>

--001a1133182c33d5a404f6a145ac--