Aleksey Yeschenko has an interesting post about the impact deletes can have on Cassandra and different workaround solutions:
Specifically, tombstones will bite you if you do lots of deletes (especially
column-level deletes) and later perform slice queries on rows with a lot of
I wouldn’t call this a “you got your data model wrong”, but rather a known implementation limitation that has impact on some scenarios in which a different data model should be used; the difference, while only semantic, is that the error is not on the user.
In other words, if you use column-level deletes (or expiring columns)
heavily and also need to perform slice queries over that data, try grouping
columns with close “expiration date” together and getting rid of them in a
Original title and link: Cassandra anti-patterns: Queues and queue-like datasets or when Deletes can bite ( ©myNoSQL)