cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Esken (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-13005) Cassandra TWCS is not removing fully expired tables
Date Tue, 06 Dec 2016 11:11:36 GMT


Christian Esken commented on CASSANDRA-13005:

Cassandra is v3.0.5. When running sstabledump (from either 3.0.5 or 3.9), we get a NullPointer

~/apache-cassandra-3.9/tools/bin/sstabledump /appdata/mc-53346-big-Data.db
Exception in thread "main" java.lang.NullPointerException
        at org.apache.cassandra.utils.FBUtilities.newPartitioner(

> Cassandra TWCS is not removing fully expired tables
> ---------------------------------------------------
>                 Key: CASSANDRA-13005
>                 URL:
>             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

View raw message