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 pair is in the query). On Tue, Apr 23, 2019 at 7:44 AM Fd Habash <fmhab...@gmail.com> wrote: > 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 a RAC that simply does not have the > data. Subsequent attempts hit another RAC that has it which triggers a read > repair causing the row to be returned consistently afterwards. Is this > correct? > > > > If a coordinator picks a node in the same RAC and the node does not have > the data on disk, is it going to stop there and return nothing even though > the row does exist on another RAC? > > > > If anti-entropy repair has completed successfully on the entire cluster > ‘repair -pr’, why is this still happening? > > > > > > ---------------- > Thank you > > >
