Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-8340

Use sstable min timestamp when deciding if an sstable should be included in DTCS compactions

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Low
    • Resolution: Won't Fix
    • None
    • None

    Description

      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 Björn Hegerfors ?

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned Assign to me
            marcuse Marcus Eriksson
            Votes:
            2 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Issue deployment