Thanks everyone for your responses. We have columns with list<text> and list<int> types, and after using sstabledump, we found that the tombstones are being generated due to these columns.
I’ve encountered another issue related to tombstones in a table that is not involved in any write operations, as it is solely used for data processing. Despite no update or delete operations occurring, I'm observing one tombstone scanned per query. The TTL is set to 0, and I’ve manually attempted to compact the table on each node, yet the tombstone remains. What could be the possible reason for this behavior? On Wed, Oct 9, 2024 at 10:32 AM Jon Haddad <j...@rustyrazorblade.com> wrote: > Are you using collections? > > — > Jon Haddad > Rustyrazorblade Consulting > rustyrazorblade.com > > > On Tue, Oct 8, 2024 at 10:52 PM Naman kaushik <namankaush...@gmail.com> > wrote: > >> Hi Community, >> >> We are currently using Cassandra version 4.1.3 and have encountered an >> issue related to tombstone generation. We have two tables storing monthly >> data: table_september and table_october. Each table has a TTL of 30 days. >> >> For the month of October, data is being inserted into the table_october, >> and we are seeing the following warning at the start of the month: >> >> *WARN [CompactionExecutor:22030] 2024-10-07 16:37:16,376 >> BigTableWriter.java:274 - Writing 102594 tombstones to **table_october* >> >> *Here are a few things to note*: >> >> - No update or delete operations are being performed on the table. >> - TTL is correctly set to 30 days, and the data being inserted is >> within this time range, so the TTL shouldn't be the reason for tombstones. >> - No null values are being inserted in any column. >> >> We are still seeing tombstones being generated for the October table. >> Does anyone have insights into what could be causing these tombstones, or >> how we can prevent this from happening? >> >> Any help would be greatly appreciated! >> >> Thanks in advance. >> >
