Same answer ; just wait for the StochasticLoadBalancer (currently in trunk)
On Wed, Dec 5, 2012 at 7:05 AM, Stack wrote:
> On Tue, Dec 4, 2012 at 8:57 PM, Liu, Raymond
> wrote:
>
> > Hi
> >
> > I am just curious about the region assignment strategy upon table
> > re-enabling.
> >
On Tue, Dec 4, 2012 at 8:57 PM, Liu, Raymond 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
>
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 prev
I guess you only have 1 table and you write to it sequentially such
that the regions that get moved are the ones you're not writing to?
Then yeah it's unusable but also you might be doing wrong (if that's
really your situation). You need to make sure you don't end up writing
to the latest regions,
Jack Levin writes:
>
> I am on 0.89-830
>
> On Tue, Mar 29, 2011 at 10:44 AM, Ted Yu wrote:
> > Are you using 0.90.1 (where regions are randomly distributed across cluser)
> > ?
> > I logged HBASE-3373 but was told it is specific to our usage.
> >
> > On Tue, Mar 29, 2011 at 10:39 AM, Jack Lev
I am on 0.89-830
On Tue, Mar 29, 2011 at 10:44 AM, Ted Yu wrote:
> Are you using 0.90.1 (where regions are randomly distributed across cluser)
> ?
> I logged HBASE-3373 but was told it is specific to our usage.
>
> On Tue, Mar 29, 2011 at 10:39 AM, Jack Levin wrote:
>
>> Hello, we have this one
Are you using 0.90.1 (where regions are randomly distributed across cluser)
?
I logged HBASE-3373 but was told it is specific to our usage.
On Tue, Mar 29, 2011 at 10:39 AM, Jack Levin wrote:
> Hello, we have this one table what about 12 regions, that is super hot
> with writes, for some reason
Hello, we have this one table what about 12 regions, that is super hot
with writes, for some reason most of the regions were assigned to a
single server, which cause it to flush and compact every 10 minutes,
causing suboptimal performance. We do use random row_keys, so I don't
see how sorted ROWs
