Balancer distributes regions among RS's - not equalizes them. You, probably, have very serious data skew and not optimal key design. I would suggest you to try custom region split policy and provide your own split key, because standard splitting algorithm does not work well. On Jun 18, 2015 7:50 AM, "Nasron Cheong" <nas...@gmail.com> wrote:
> Hi, > > I've noticed there are two settings available when using the HBase balancer > (specifically the default stochastic balancer) > > hbase.master.balancer.stochastic.tableSkewCost > > hbase.master.loadbalance.bytable > > How do these two settings relate? The documentation indicates when using > the stochastic balancer that 'bytable' should be set to false? > > Our deployment relies on very few, very large tables, and I've noticed bad > distribution when accessing some of the tables. E.g. there are 443 regions > for a single table, but when doing a MR job over a full scan of the table, > the first 426 regions scan quickly (minutes), but the remaining 17 regions > take significantly longer (hours) > > My expectation is to have the balancer equalize the size of the regions for > each table. > > Thanks! > > - Nasron >
