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

Possible data loss on upgrade 2.1 - 3.0

    XMLWordPrintableJSON

    Details

    • Severity:
      Critical

      Description

      After finishing a compaction we delete the compacted away files. This is done here which uses this to get the files - we get all files starting with absoluteFilePath. Absolute file path is generated here. For 3.0 version files the filename looks like this: /blabla/keyspace1/standard1-bdb031c0ff7b11e6940fdd0479dd8912/mc-1332-big but for 2.1 version files, they look like this: /blabla/keyspace1/standard1-bdb031c0ff7b11e6940fdd0479dd8912/keyspace1-standard1-ka-2.

      The problem is then that if we were to finish a compaction including the legacy file, we would actually delete all legacy files having a generation starting with '2'

        Attachments

          Activity

            People

            • Assignee:
              Stefania Stefania
              Reporter:
              krummas Marcus Eriksson
              Authors:
              Stefania
              Reviewers:
              Marcus Eriksson
            • Votes:
              1 Vote for this issue
              Watchers:
              14 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: