Hi Jaydeep.
> 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.
This is an acceptable situation (ie. a
Hi Jaydeep,
Yes, dealing with tombstones in Cassandra is very tricky.
Cassandra keeps tombstones to mark deleted columns and distribute (hinted
handoff, full repair, read repair ...) to the other nodes that missed the
initial remove request. But Cassandra can't afford to keep those tombstones
lif
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
(T
