This could be because of the way you have configured the policy, have a look at the below links for configuring the policy
https://datastax.github.io/python-driver/api/cassandra/policies.html http://stackoverflow.com/questions/22813045/ability-to-write-to-a-particular-cassandra-node Regards, Bhuvan On Wed, Apr 13, 2016 at 6:54 PM, Walsh, Stephen <stephen.wa...@aspect.com> wrote: > Hi there, > > So we have 2 datacenter with 3 nodes each. > Replication factor is 3 per DC (so each node has all data) > > We have an application in each DC that writes that Cassandra DC. > > Now, due to a miss configuration in our application, we saw that our > application in both DC’s where pointing to DC1. > > As such, all keyspaces and tables where created on DC1. > The effect of this is that all reads are now going to DC1 and ignoring DC2 > > WE’ve tried doing , nodetool repair / cleanup – but the reads always go to > DC1? > > Anyone know how to rebalance the tokens over DC’s? > > > Regards > Steve > > > P.S I know about this article > http://www.datastax.com/dev/blog/balancing-your-cassandra-cluster > But its doesn’t answer my question regarding 2 DC’s token balancing > > This email (including any attachments) is proprietary to Aspect Software, > Inc. and may contain information that is confidential. If you have received > this message in error, please do not read, copy or forward this message. > Please notify the sender immediately, delete it from your system and > destroy any copies. You may not further disclose or distribute this email > or its attachments. >
