cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10015) Create tool to debug why expired sstables are not getting dropped
Date Tue, 11 Aug 2015 00:44:46 GMT

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

Stefania commented on CASSANDRA-10015:
--------------------------------------

+1 

Nits for the dtest:
* trailing spaces in one of the empty lines just under the new test 
* _import time_ is not used

> Create tool to debug why expired sstables are not getting dropped
> -----------------------------------------------------------------
>
>                 Key: CASSANDRA-10015
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10015
>             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
(v6.3.4#6332)

Mime
View raw message