Hi,
I have a single partition key that been nagging me because I am receiving org.apache.cassandra.db.filter.TombstoneOverwhelmingException. After filing https://issues.apache.org/jira/browse/CASSANDRA-8561 I managed to find the partition key in question and which machine it was located on (by looking in system.log). Since I wanted to see how many tombstones the partition key actually had I did: nodetool flush mykeyspace mytable to make sure all changes were written to sstables (not sure this was necessary), then nodetool getsstables mykeyspace mytable PARTITIONKEY which listed two sstables. I then had a look at both sstables for my key in question using sstable2json MYSSTABLE1 -k PARTITIONKEY | jq . > MYSSTABLE1.json sstable2json MYSSTABLE2 -k PARTITIONKEY | jq . > MYSSTABLE2.json (piping through jq to format the json). Both JSON files contains data (so I have selected the right key). Only one of the files contains any tombstones $ cat MYSSTABLE1.json | grep '"t"'|wc -l 4281 $ cat MYSSTABLE2.json | grep '"t"'|wc -l 0 But to my surprise, the number of tombstones are nowhere near tombstone_failure_threshold: 100000 Can anyone explain why Cassandra is overwhelmed when I’m nowhere near the hard limit? Thanks, Jens ——— Jens Rantil Backend engineer Tink AB Email: jens.ran...@tink.se Phone: +46 708 84 18 32 Web: www.tink.se Facebook Linkedin Twitter
