It is counter caused the pr=
oblem. counter will replicate to all replicas during write regardless the c=
onsistency level.=A0

In our case. we don't need to sync the counter across th=
e center. so moving counter to new keyspace and all the replica in one cent=
er=A0solved=A0problem.

There is option=A0replicate_on_write on table. If you t=
urn that off for counter might have better performance. but you are on high=
risk to lose data and create inconsistency. I did not try this option.

I am seeing the s=
imilar behavior, in my case I have 2 nodes in each datacenter and one node =
always has high latency (equal to the latency between the two datacenters).=
When one of the datacenters is shutdown the latency drops.

I am curious to know whether anyone else has these issues and if =
yes how did to get around it.

We have deployed multi-cent=
er but got performance issue. When the nodes on other center are up, the re=
ad response time from clients is 4 or 5 times higher. when we take those no=
des down, the response time becomes normal(compare to the time before we ch=
anged to multi-center).

We have high volume on the cluster, the consistency level is=
one for read. so my understanding is most of traffic between data center s=
hould be read repair. but seems that could not create much delay.