Never mind. I found the root cause. This has nothing to do with Cassandra
and repair. Some web services called by the client caused the problem.
On Fri, Aug 19, 2016 at 11:53 AM, Benyi Wang wrote:
> I'm using cassandra java driver to access a small cassandra cluster
>
> * The cluster have 3 node
I'm using cassandra java driver to access a small cassandra cluster
* The cluster have 3 nodes in DC1 and 3 nodes in DC2
* The keyspace is originally created in DC1 only with RF=2
* The client had good read latency about 40 ms of 99 percentile under 100
requests/sec (measured at the client side)
*
