I guess Pradheep's intention is to save some cost for the duration when the hbase cluster is not used.
On Wed, Mar 8, 2017 at 1:37 AM, sudhakara st <sudhakara...@gmail.com> wrote: > I believe the problem is bring down the cluster is everyday. On Hbase > start probability of re-assigns regions is more, region > re-assignment/moving region always effect the data locality. > > Regards, > Sudhakara > > On Wed, Mar 8, 2017 at 12:59 PM, Anoop John <anoop.hb...@gmail.com> wrote: > > > There is one config "hbase.master.loadbalance.bytable" using which > > user can say whether the balancing has to be done per table or > > globally balance. I believe u r using StochasticLoadBalancer only > > which is the default. > > > > The move calls are affecting ur locality? > > > > -Anoop- > > > > On Wed, Mar 8, 2017 at 1:05 AM, Pradheep Shanmugam > > <pradheep.shanmu...@infor.com> wrote: > > > Hi, > > > > > > I have a Hbase(1.1.2) cluster with 8 region servers in AWS..I bring > down > > the cluster everyday and bring it up again next day. > > > > > > Every day the locality keeps decreasing(95, 80, 70) and does not go up > > even after doing major compaction of all the tables. Why is it so? > > > Also the regions of a particular table are not gettting equally > > distrubuted after the cluster is up..I have to run the hbase move > commands > > to move the table regions around..but the locality does not go up even > > after this.. > > > But the overall regions are distributed equally across the region > > servers. I guess this is done by the balancer. > > > > > > Thanks, > > > Pradheep > > > > > > -- > > Regards, > ...sudhakara >
