it will take half of G's range. Problem is, it will take
half of G's _primary_ range, but most of G's load comes from
_replicas_.
From looking at the code recently, it chooses a token that splits G's load by
actually sampling the data stored on G, which should make the primary vs
replica
On Tue, Feb 9, 2010 at 3:13 AM, Jaakko rosvopaalli...@gmail.com wrote:
What they probably should do, is to just
consider nodes in the DC they are booting to, and try to balance load
evenly in that DC.
I'm not sure what problem that would solve. It seems to me there are two goals:
1. don't
Coe robin@bluecoat.com
Sent: Tuesday, February 9, 2010 12:58pm
To: cassandra-dev@incubator.apache.org
Subject: Re: loadbalance and different strategies
Is it true that it is no longer necessary to specify an initial token?
If so, how would you add a new node into a ring such that it guarantees
: loadbalance and different strategies
Is it true that it is no longer necessary to specify an initial token?
If so, how would you add a new node into a ring such that it guarantees
replicas are spread evenly across data centres? Is this achieved simply
by starting a new node in the opposite DC
-
From: Robin Coe robin@bluecoat.com
Sent: Tuesday, February 9, 2010 1:48pm
To: cassandra-dev@incubator.apache.org
Cc: cassandra-us...@bluecoat.com
Subject: Re: loadbalance and different strategies
Thanks for the link, Stu.
So, from what I gather, initial tokens are required for seed nodes
(2) is where we get into trouble here no matter which DC we add to.
(a) if we add to G's DC, X will get all the replicas G has, remaining
unbalanced
(b) if we add to the other DC, G will still be hit from all the
replicas from the other DC
2b: yes
2a: not necessarily. Let's return once
; cassandra-us...@bluecoat.com
Subject: Re: loadbalance and different strategies
In 0.5, nodes can be automatically rebalanced one at a time using the 'nodetool
loadbalance' command, mentioned on that page (although, admittedly, it is in
the wrong section).
'nodetool flush' has nothing to do
On Tue, Feb 9, 2010 at 6:12 PM, Jaakko rosvopaalli...@gmail.com wrote:
Let us suppose that all ranges are equal in size. In this case G's
range is A-G. If X boots in G's DC, it should take a token in the
middle of this range, which would be somewhere around D. If X boots
behind D
Ah, I see,
On Tue, Feb 9, 2010 at 9:45 PM, Jonathan Ellis jbel...@gmail.com wrote:
That seems reasonable, although it feels a little weird for X to as G
for a token and be given one that G isn't the primary for.
for X to ask* G
On Wed, Feb 10, 2010 at 12:45 PM, Jonathan Ellis jbel...@gmail.com wrote:
On Tue, Feb 9, 2010 at 6:12 PM, Jaakko rosvopaalli...@gmail.com wrote:
Let us suppose that all ranges are equal in size. In this case G's
range is A-G. If X boots in G's DC, it should take a token in the
middle of this
point moot.
-Original Message-
From: Jaakko rosvopaalli...@gmail.com
Sent: Tuesday, February 9, 2010 12:51am
To: cassandra-dev@incubator.apache.org
Subject: loadbalance and different strategies
Hi,
Current implementation of loadbalance seems to work only for
RackUnaware. Problem is only
11 matches
Mail list logo
