Thanks,
Chong
On Thu, May 31, 2012 at= 9:52 PM, aaron morton wrote= :
The ring (2 in DC1, 1 in DC2) look= s OK, but the load on the new node in DC2 is almost 0%.
yeah, thats the way it will look.=A0

But = all the other rows are not in the new node. Do I need to copy the data file= s from a node in DC1 to the new node?

if in doubt run nodetool repair on the new node.=A0

Cheers

<= div style=3D"word-wrap:break-word">
-----------------
Aaron Morton
Freelance Deve= loper
@aaronmorton

On 1/06/2012, at 3:46 AM, Chong = Zhang wrote:

Thanks Aaron.

I might use LOCAL_QUORUM to avoid the waiting on the ack from DC2.

Another question, after I setup a new node with token += 1 in a new DC, =A0and updated a CF with RF {DC1:2, DC2:1}. When i update a = column on one node in DC1, it's also updated in the new node in DC2. Bu= t all the other rows are not in the new node. Do I need to copy the data fi= les from a node in DC1 to the new node?

The ring (2 in DC1, 1 in DC2) looks OK, but the load on= the new node in DC2 is almost 0%.

Address = =A0 =A0 =A0 =A0 DC =A0 =A0 =A0 =A0 =A0Rack =A0 =A0 =A0 =A0Status State =A0 = Load =A0 =A0 =A0 =A0 =A0 =A0Owns =A0 =A0Token =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=A0
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A085070591730234615865843651857942052864 =A0 =A0 =A0
10.10.10.1 =A0 =A0DC1 =A0 =A0 =A0 =A0 RAC1 =A0 =A0 =A0 =A0Up =A0 =A0 Norm= al =A0313.99 MB =A0 =A0 =A0 50.00% =A00 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=A0
10.10.10.3 =A0 =A0DC2 =A0 =A0 =A0 =A0 RAC1 =A0 =A0 =A0 =A0Up =A0 =A0 N= ormal =A07.07 MB =A0 =A0 =A0 =A0 =A0 0.00% =A0 1 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=A0
10= .10.10.2 =A0 =A0DC1 =A0 =A0 =A0 =A0 RAC1 =A0 =A0 =A0 =A0Up =A0 =A0 Normal = =A0288.91 MB =A0 =A0 =A0 50.00% =A085070591730234615865843651857942052864 = =A0 =A0 =A0

Thanks,
Chong

On Thu, May 31, 2012 at 5:48 AM, aaron morton &l= t;aaron@thelas= tpickle.com> wrote:

Could you provide some guide on how to assign the tokens in thi= s growing deployment phases?=A0

background=A0ht= tp://www.datastax.com/docs/1.0/install/cluster_init#calculating-tokens-for-= a-multi-data-center-cluster

Start with tokens for a 4 node cluster. Add the next 4 = between between each of the ranges. Add 8 in the new DC to have the same to= kens as the first DC +1

Also if we use the same RF (3) in both DC, and use=A0EACH_QUORUM for write and=A0LOCAL_QUORUM f= or read, can the read also reach to the 2nd cluster?
No. It will fail if there are not enough nodes available= in the first DC.=A0

We'd like to keep both write and read on the same cl= uster.
Writes go to all replicas. Using EACH_QUORUM means the c= lient in the first DC will be waiting for the quorum from the second DC to = ack the write.=A0

Cheers
<= div style=3D"word-wrap:break-word">
-----------------
Aaron Morton
Freelance Deve= loper
@aaronmorton

On 31/05/2012, at 3:20 AM, Chong Zhang wrote:

Hi all,

We are planning to deploy a = small cluster with 4 nodes in one DC first, and will expend that to 8 nodes= , then add another DC with 8 nodes for fail over (not active-active), so al= l the traffic will go to the 1st cluster, and switch to 2nd cluster if the = whole 1st cluster is down or on=A0maintenance.=A0

Could you provide some guide on how to assign the token= s in this growing deployment phases? I looked at some docs but not very cle= ar on how to assign tokens on the fail-over case.
Also if we use = the same RF (3) in both DC, and use=A0EACH_Q= UORUM for write and=A0LOCAL_QUORUM for read, can the rea= d also reach to the 2nd cluster? We'd like to keep both write and read = on the same cluster.