cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8340) Use sstable min timestamp when deciding if an sstable should be included in DTCS compactions
Date Wed, 19 Nov 2014 21:24:33 GMT

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

Marcus Eriksson commented on CASSANDRA-8340:
--------------------------------------------

I meant using max timestamp in filterOldSSTables to avoid compacting the big sstable at all

> Use sstable min timestamp when deciding if an sstable should be included in DTCS compactions
> --------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-8340
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8340
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Marcus Eriksson
>            Priority: Minor
>
> Currently we check how old the newest data (max timestamp) in an sstable is when we check
if it should be compacted.
> If we instead switch to using min timestamp for this we have a pretty clean migration
path from STCS/LCS to DTCS. 
> My thinking is that before migrating, the user does a major compaction, which creates
a huge sstable containing all data, with min timestamp very far back in time, then switching
to DTCS, we will have a big sstable that we never compact (ie, min timestamp of this big sstable
is before max_sstable_age_days), and all newer data will be after that, and that new data
will be properly compacted
> WDYT [~Bj0rn] ?



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

Mime
View raw message