[
https://issues.apache.org/jira/browse/CASSANDRA-13005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15725169#comment-15725169
]
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 Exception.
{code}
~/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(FBUtilities.java:429)
at
org.apache.cassandra.tools.SSTableExport.metadataFromSSTable(SSTableExport.java:104)
at org.apache.cassandra.tools.SSTableExport.main(SSTableExport.java:180)
{code}
> 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)
