[ https://issues.apache.org/jira/browse/CASSANDRA-8340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14567181#comment-14567181 ]
Etienne Adam commented on CASSANDRA-8340: ----------------------------------------- I didn't know DTCS and read repair were incompatible.. But I can still run nodetool repair, isn'it ? >From my understanding of Cassandra, read repair or nodetool repair are >mandatory to have a sane cluster over time.. Am I wrong ? > 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 > Attachments: 8340-v2.diff, 8340.diff > > > 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)