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

CFS.CANONICAL_SSTABLES adds compacting sstables without checking if they are still live

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Normal
    • Resolution: Unresolved
    • 2.1.x, 2.2.x
    • None
    • None
    • Normal

    Description

      In 2.1 and 2.2 we blindly add all compacting sstables to the ColumnFamilyStore.CANONICAL_SSTABLES

      This could cause issues as we unmark compacting after removing sstables from the tracker and compaction strategies. For example, when creating scanners for validation with LCS we might get overlap within a level as both the old sstables and the new ones could be in CANONICAL_SSTABLES

      What we need to do is to get the version of the sstable from the compacting set as it holds the original sstable without moved starts etc (that is what we do in 3.0+)

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              marcuse Marcus Eriksson
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated: