Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 6 Dec 2016 13:58:58 +0000 (UTC)
From: "Christian Esken (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.13025931.1481022069000.450048.1481032738538@Atlassian.JIRA>
In-Reply-To: <JIRA.13025931.1481022069000@Atlassian.JIRA>
References: <JIRA.13025931.1481022069000@Atlassian.JIRA> <JIRA.13025931.1481022069431@arcas>
Subject: [jira] [Updated] (CASSANDRA-13005) Cassandra TWCS is not removing
 fully expired tables
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 06 Dec 2016 13:59:00 -0000


     [ https://issues.apache.org/jira/browse/CASSANDRA-13005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Esken updated CASSANDRA-13005:
----------------------------------------
    Description: 
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 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)


  was:
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 file 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


> 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 / Casandra 3.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
>         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 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)