A keyspace with RF=3, Cluster with 3 RACS, CL=LQ: No Data on First Attempt, but 1 Row Aftwards

Cluster setup … - C* 2.2.8 - Three RACs, one DC - Keyspace with RF=3 - RS = Network topology At CL=LQ … I get zero rows on first attempt, and one row on the second or third. Once found, I always get the row afterwards. Trying to understand this behavior … First attempt, my read request hits

Re: Unpair cassandra datacenters

Thanks Sandeep for your reply. Let me try out the steps you suggested. I will let you know. Appreciate your help. Regards, Kunal Vaid On Mon, Apr 22, 2019 at 4:18 PM Sandeep Nethi wrote: > Hi Kunal, > > The simple solution for this case would be as follows, > > 1. Run *Full repair.* > 2. Add f

RE: A keyspace with RF=3, Cluster with 3 RACS, CL=LQ: No Data on FirstAttempt, but 1 Row Aftwards

Any ideas, please? Thank you From: Fd Habash Sent: Tuesday, April 23, 2019 10:38 AM To: user@cassandra.apache.org Subject: A keyspace with RF=3, Cluster with 3 RACS, CL=LQ: No Data on FirstAttempt, but 1 Row Aftwards Cluster setup … - C* 2.2.8 - Three RACs, one DC - Keyspace w

Re: A keyspace with RF=3, Cluster with 3 RACS, CL=LQ: No Data on First Attempt, but 1 Row Aftwards

Sounds like you're writing at ONE and reading at LOCAL_QUORUM. If you call your hosts A,B,C Your write lands on B If your query hits A and C, you return 0 rows. If your query hits A and B or B and C, you return 1 row AND (as a side effect) the row is copied to either A or C (depending on which p

A cluster (RF=3) not recovering after two nodes are stopped

Hello, I faced a weird issue when recovering a cluster after two nodes are stopped. It is easily reproduce-able and looks like a bug or an issue to fix, so let me write down the steps to reproduce. === STEPS TO REPRODUCE === * Create a 3-node cluster with RF=3 - node1(seed), node2, node3 * Sta

Re: A cluster (RF=3) not recovering after two nodes are stopped

Is it possible that stress is overloading node 1 so it’s not recovering state properly when node 2 comes up? Have you tried running with a lower load (say 2 or 3 threads)? Cheers Ben --- *Ben Slater* *Chief Product Officer*