On Wed, Nov 13, 2013 at 5:34 AM, Katriel Traum wrote:
> Thats it! I knew NetworkTopologyStrategy goes through racks when writing,
> but didn't consider that the first one will most likely be used.
>
> I'll re-arrange my nodes to be a,b,c,a,b,c
>
https://issues.apache.org/jira/browse/CASSANDRA-38
Thats it! I knew NetworkTopologyStrategy goes through racks when writing,
but didn't consider that the first one will most likely be used.
I'll re-arrange my nodes to be a,b,c,a,b,c
Thanks,
Katriel
On Wed, Nov 13, 2013 at 3:15 PM, Derek Williams wrote:
> The problem is that NetworkTopologyStr
The problem is that NetworkTopologyStrategy will try to pick nodes that
have a different rack when going around the ring, so the second node in
each rack always gets skipped unless it was the first node picked. Your
nodes is eu-west go a,a,b,b,c,c but they should be a,b,c,a,b,c.
On Wed, Nov 13, 2
Hello Katriel,
Are you using replication factor 3? So it seems that in us-east it's all
fine with each machine having 100% of the data. The problem is in eu-west
where you have unbalanced nodes. You should rearrange the tokens in that
eu-west DC.
Check e.g. this token calculator to calculate good
Hello list,
I have a problem with my cluster ownership not being as expected.
I have 2 DC cluster using NetworkTopologyStrategy on and
EC2MultiRegionSnitch with cassandra 1.1.5. My placement strategy for all
keyspaces is: {eu-west: 3, us-east:3 }, and I have 6 nodes in eu-west and 3
in us-east.
I
