Hi,

We have three node (N1, N2, N3) cluster (RF=3) and data in SSTable as
following:

N1:
SSTable: Partition key K1 is marked as tombstone at time T2

N2:
SSTable: Partition key K1 is marked as tombstone at time T2

N3:
SSTable: Partition key K1 is valid and has data D1 with lower time-stamp T1
(T1 < T2)


Now when I read using quorum then sometimes it returns data D1 and
sometimes it returns empty results. After tracing I found that when N1 and
N2 are chosen then we get empty data, when (N1/N2) and N3 are chosen then
D1 data is returned.

My point is when we read with Quorum then our results have to be
consistent, here same query give different results at different times.

Isn't this a big problem with Cassandra @QUORUM (with tombstone)?


Thanks,
Jaydeep

Reply via email to