[CASSANDRA-13294] Possible data loss on upgrade 2.1 - 3.0

• Type: Bug
• Status: Resolved
• Priority: Urgent
• Resolution: Fixed
• Fix Version/s: 3.0.12, 3.11.0
• Component/s: Legacy/Local Write-Read Paths
• Severity: Critical
• Assignee: Stefania Alborghetti
• Reporter: Marcus Eriksson

Authors

Stefania Alborghetti

Reviewers

Marcus Eriksson

• Created: 03/Mar/17 10:03
• Updated: 16/Apr/19 09:30
• Resolved: 07/Mar/17 01:22

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'