cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Esken (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13005) Cassandra TWCS is not removing fully expired tables
Date Thu, 12 Jan 2017 13:51:52 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-13005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15821041#comment-15821041
] 

Christian Esken commented on CASSANDRA-13005:
---------------------------------------------

While the issue was not present in the last 4 weeks, it now has happened again. I am adding
the sstableexpiredblockers output, as requested:

{code}
# sstableexpiredblockers cachestore bookinglinkentries [BigTableReader(path='/data/cassandra/data/cachestore/bookinglinkentries-a2502c60bba511e6917fcda6eb6df2bb/mc-204995-big-Data.db')
(minTS = 1484213395148001, maxTS = 1484214299952743, maxLDT = 1484228699)],  blocks 1 expired
sstables from getting dropped: [BigTableReader(path='/data/cassandra/data/cachestore/bookinglinkentries-a2502c60bba511e6917fcda6eb6df2bb/mc-205731-big-Data.db')
(minTS = 1484212495197503, maxTS = 1484213395210562, maxLDT = 1484227795)],
{code}

The broken SSTables do not appear in the sstableexpiredblockers output. As last time, the
number of SSTables keeps increasing once the problem has occurred initially.


> 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: Cassandra 3.0.9
> Java HotSpot(TM) 64-Bit Server VM version 25.112-b15 (Java version 1.8.0_112-b15)
> Linux 3.16
>            Reporter: Christian Esken
>              Labels: twcs
>         Attachments: sstablemetadata-empty-type-that-is-3GB.txt
>
>
> I 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 file creation timestamp), but the number of tables is growing.
Analysis and actions take so far:
> - sstablemetadata shows strange data, as if the table is completely empty.
> - sstabledump throws an Exception when running it on such a SSTable
> - Even triggering a manual major compaction will not remove the old SSTable's. To be
more precise: They are recreated with new id and timestamp (not sure whether they are identical
as I cannot inspect content due to the sstabledump crash)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message