Hi

I am just curious about the region assignment strategy upon table re-enabling.
By default, it's random assigned to the region server. I checked jira and found HBASE-6143 suggest to make it smarter like take load balancing into account.
While, I am wondering what prevent it from using the retain assignment strategy as in the case that a hbase cluster is restarting? Is there any reason that we cannot use the previous region assignments in META table?

Best Regards,
Raymond Liu

On Tue, Dec 4, 2012 at 8:57 PM, Liu, Raymond <[EMAIL PROTECTED]> wrote:

> Hi
>
>         I am just curious about the region assignment strategy upon table
> re-enabling.
>         By default, it's random assigned to the region server. I checked
> jira and found HBASE-6143 suggest to make it smarter like take load
> balancing into account.
>         While, I am wondering what prevent it from using the retain
> assignment strategy as in the case that a hbase cluster is restarting? Is
> there any reason that we cannot use the previous region assignments in META
> table?
>

Not that I know of.
St.Ack

Same answer ; just wait for the StochasticLoadBalancer (currently in trunk)
On Wed, Dec 5, 2012 at 7:05 AM, Stack <[EMAIL PROTECTED]> wrote:

> On Tue, Dec 4, 2012 at 8:57 PM, Liu, Raymond <[EMAIL PROTECTED]>
> wrote:
>
> > Hi
> >
> >         I am just curious about the region assignment strategy upon table
> > re-enabling.
> >         By default, it's random assigned to the region server. I checked
> > jira and found HBASE-6143 suggest to make it smarter like take load
> > balancing into account.
> >         While, I am wondering what prevent it from using the retain
> > assignment strategy as in the case that a hbase cluster is restarting? Is
> > there any reason that we cannot use the previous region assignments in
> META
> > table?
> >
>
> Not that I know of.
> St.Ack
>

--
Adrien Mogenet
06.59.16.64.22
http://www.mogenet.me