You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hbase.apache.org by Tao Xiao <xi...@gmail.com> on 2014/05/29 03:49:56 UTC

What property would trigger a region split besides hbase.hregion.max.filesize ?

I hope each region can be 10GB in size, so I set the property
*hbase.hregion.max.filesize* as 10737418240, which is 10GB. Then I
restarted the HBase cluster.

To check whether this property works, I created a new table and wrote  a
lot of records into it. However, when I checked the size of the regions of
that table, I found that each region is far smaller than 10GB. Actually,
regions of that table are about 3GB in size.

I guess there are other factors that would trigger a region split, albeit I
set the property *hbase.hregion.max.filesize* as 10GB.  Am I right ?

Thanks.


Tao

Re: What property would trigger a region split besides hbase.hregion.max.filesize ?

Posted by Tao Xiao <xi...@gmail.com>.
Ted,

I'm using HBase 0.96.1.2.0.6.1 (HDP 2.0.6).

I set the regionserver log level to *INFO*, so I did not find any log
containing "SplitPolicy". I will set the log level to *DEBUG *and take a
look at regionserver log later.

Thanks



Tao


2014-05-29 10:32 GMT+08:00 Ted Yu <yu...@gmail.com>:

> Which HBase release are you using ?
>
> Can you look in the region server log which SplitPolicy is in effect ?
> Below is a sample log snippet:
>
> 2014-04-09 15:35:03,737 DEBUG [MemStoreFlusher.0]
> regionserver.IncreasingToUpperBoundRegionSplitPolicy: ShouldSplit because
>
>
> On Wed, May 28, 2014 at 6:49 PM, Tao Xiao <xi...@gmail.com>
> wrote:
>
> > I hope each region can be 10GB in size, so I set the property
> > *hbase.hregion.max.filesize* as 10737418240, which is 10GB. Then I
> > restarted the HBase cluster.
> >
> > To check whether this property works, I created a new table and wrote  a
> > lot of records into it. However, when I checked the size of the regions
> of
> > that table, I found that each region is far smaller than 10GB. Actually,
> > regions of that table are about 3GB in size.
> >
> > I guess there are other factors that would trigger a region split,
> albeit I
> > set the property *hbase.hregion.max.filesize* as 10GB.  Am I right ?
> >
> > Thanks.
> >
> >
> > Tao
> >
>

Re: What property would trigger a region split besides hbase.hregion.max.filesize ?

Posted by Ted Yu <yu...@gmail.com>.
Which HBase release are you using ?

Can you look in the region server log which SplitPolicy is in effect ?
Below is a sample log snippet:

2014-04-09 15:35:03,737 DEBUG [MemStoreFlusher.0]
regionserver.IncreasingToUpperBoundRegionSplitPolicy: ShouldSplit because


On Wed, May 28, 2014 at 6:49 PM, Tao Xiao <xi...@gmail.com> wrote:

> I hope each region can be 10GB in size, so I set the property
> *hbase.hregion.max.filesize* as 10737418240, which is 10GB. Then I
> restarted the HBase cluster.
>
> To check whether this property works, I created a new table and wrote  a
> lot of records into it. However, when I checked the size of the regions of
> that table, I found that each region is far smaller than 10GB. Actually,
> regions of that table are about 3GB in size.
>
> I guess there are other factors that would trigger a region split, albeit I
> set the property *hbase.hregion.max.filesize* as 10GB.  Am I right ?
>
> Thanks.
>
>
> Tao
>