cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10015) Create tool to debug why expired sstables are not getting dropped
Date Mon, 10 Aug 2015 08:49:46 GMT


Marcus Eriksson commented on CASSANDRA-10015:

bq. Do we need a Windows script and why do we have some sstable* scripts in bin and some in
I will add one in 2.1 as that is where we started supporting Windows
bq. In the documentation at the top of SSTableExpiredBlocker I would reference the ticket
number and perhaps explicitly spell out how an sstable can block expired sstables, rather
than just limiting it to "cover anything in other sstables". Something like what's mentioned
in this ticket description would maybe be a little clearer.
bq. I would replace columnfamily with table, at least in the usage and error messages.
fixed, will rename variables in 3.0+

which requires this ccm patch:
and nits fixed here:

> Create tool to debug why expired sstables are not getting dropped
> -----------------------------------------------------------------
>                 Key: CASSANDRA-10015
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Marcus Eriksson
>            Assignee: Marcus Eriksson
>             Fix For: 3.x, 2.1.x, 2.0.x, 2.2.x
> Sometimes fully expired sstables are not getting dropped, and it is a real pain to manually
find out why.
> A tool that outputs which sstable blocks (by having older data than the newest tombstone
in an expired sstable) expired ones would save a lot of time.

This message was sent by Atlassian JIRA

View raw message