You are right, good catch, thanks!
Wait, his nodes are going SC, SC, AT, AT. Shouldn't they go SC, AT, SC, AT? By which I mean that if he adds another node to the ring (or lowers the replication factor), he will have a node that is under-utilized. The rings in his data centers have the tokens:
SC: 0, 1
AT: 85070591730234615865843651857942052864, 85070591730234615865843651857942052865
They should be:
SC: 0, 85070591730234615865843651857942052864
AT: 1, 85070591730234615865843651857942052865
Or did I forget/misread something?
----- Original Message -----
From: "aaron morton" <email@example.com>
Sent: Tuesday, September 13, 2011 6:19:16 PM
Subject: Re: Configuring multi DC cluster
Looks good to me. Last time I checked the Partitioner did not take the DC into consideration https://issues.apache.org/jira/browse/CASSANDRA-3047
Freelance Cassandra Developer
On 14/09/2011, at 8:41 AM, Anand Somani wrote:
Just trying to setup a cluster of 4 nodes for multiDC scenario - with 2 nodes in each DC. This is all on the same box just for testing the configuration aspect. I have configured things as
• 127.0.0.4=SC:rack1 127.0.0.5=SC:rack2 127.0.0.6=AT:rack1 127.0.0.7=AT:rack2 # default for unknown nodes default=SC:rack1
Setup initial tokens as - advised • configured keyspace with SC:2, AT:2
• ring looks like
• Address Status State Load Owns Token 85070591730234615865843651857942052865 127.0.0.4 Up Normal 464.98 KB 50.00% 0 127.0.0.5 Up Normal 464.98 KB 0.00% 1 127.0.0.6 Up Normal 464.99 KB 50.00% 85070591730234615865843651857942052864 127.0.0.7 Up Normal 464.99 KB 0.00% 85070591730234615865843651857942052865
Is that what I should expect the ring to look like? Is there anything else I should be testing/validating to make sure that things are configured correctly for NTS?