You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Christian Esken (JIRA)" <ji...@apache.org> on 2016/12/06 11:11:36 UTC
[jira] [Created] (CASSANDRA-13005) Cassandra TWCS is not removing
fully expired tables
Christian Esken created CASSANDRA-13005:
-------------------------------------------
Summary: Cassandra TWCS is not removing fully expired tables
Key: CASSANDRA-13005
URL: https://issues.apache.org/jira/browse/CASSANDRA-13005
Project: Cassandra
Issue Type: Bug
Components: Compaction
Environment: Linux
Cassandra 3.0.5 / Casandra 3.9
Reporter: Christian Esken
Attachments: sstablemetadata-empty-type-that-is-3GB.txt
We have a table where all columns are stored with TTL of maximum 4 hours. Usually TWCS compaction properly removes expired data via tombstone compaction and also removes fully expired tables. The number of SSTables is nearly constant since weeks. Good.
The problem: Suddenly TWCS does not remove old SSTables any longer. They are being recreated frequently (judging form the filer creation timestamp), but the number of tables is growing.
- sstablemetadata shows strange data, as if the table is completely empty.
- sstabledump throws an Exception when running it on such a SSTable
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)