I’ve added an option to prevent tombstone creation when using
PreparedStatements to trunk, see CASSANDRA-7304.
The problem is having tombstones in regular columns.
When you perform a read request (range query or by PK):
- Cassandra iterates over all the cells (all, not only the cells specified in
I agree that inserting null is not as good as not inserting that column at
all when you have confidence that you are not shadowing any underlying
data. But pragmatically speaking it really doesn't sound like a small
number of incidental nulls/tombstones (< 20% of columns, otherwise
CASSANDRA-3442 t
Hi,
as it turned out, the problem was that our secondary DC was indeed
overloaded and therefore dropped read requests which where executed during
connection establishment.
The cause of this overload might be interesting: Actually we ran reversed
values for dclocal_read_repair_chance and read_repa
