.
Enjoy!
From: Ayub M [mailto:hia...@gmail.com]
Sent: Saturday, February 23, 2019 4:36 AM
To: user@cassandra.apache.org
Subject: Re: tombstones threshold warning
Thanks Ken, further investigating what I found is the tombstones which I am
seeing are from null values in the collection
Executing single-partition query on
collsndudt [CoreThread-6] | 2019-02-21 21:41:04.629001 | 10.216.87.180
|460 | 127.0.0.1
Acquiring sstable
references [CoreThread-6] | 2019-02-21 21:41:04.629001 | 10.216.87.
...@yahoo.com]
Sent: Tuesday, February 19, 2019 10:12 PM
To: 'user@cassandra.apache.org'
Subject: RE: tombstones threshold warning
Hi Ayub,
Is everything flushing to SSTables? It has to be somewhere right? So is it in
the memtables?
Or is it that there are tombstones that are
M [mailto:hia...@gmail.com]
Sent: Saturday, February 16, 2019 9:58 PM
To: user@cassandra.apache.org
Subject: tombstones threshold warning
In the logs I see tombstone warning threshold.
Read 411 live rows and 1644 tombstone cells for query SELECT * FROM ks.tbl
WHERE key = XYZ LIMIT 5000 (see
In the logs I see tombstone warning threshold.
Read 411 live rows and 1644 tombstone cells for query SELECT * FROM ks.tbl
WHERE key = XYZ LIMIT 5000 (see tombstone_warn_threshold)
This is Cassandra 3.11.3, I see there are 2 sstables for this table and the
partition XYZ exists in only one file. No
