Hey guys, I have a table with RF=3 and LCS. Data model makes use of "wide rows". A certain query run against this table times out and tracing reveals the following error on two out of three nodes:
*Scanned over 100000 tombstones; query aborted (see tombstone_failure_threshold)* This basically means every request with CL higher than "one" fails. I have two questions: * How could it happen that only two out of three nodes have overwhelming tombstones? For the third node tracing shows sensible *"Read 815 live and 837 tombstoned cells"* traces. * Anything I can do to fix those two nodes? I have already set gc_grace to 1 day and tried to make compaction strategy more aggressive (unchecked_tombstone_compaction - true, tombstone_threshold - 0.01) to no avail - a couple of days have already passed and it still gives the same error. Thanks! Roman
