[CASSANDRA-12565] Node may not start when upgrading from 2.2 to 3.0 if drain is not run

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.0.9, 3.10
• Component/s: Legacy/Local Write-Read Paths
• Severity: Normal
• Assignee: Stefania Alborghetti
• Reporter: Stefania Alborghetti

Authors

Stefania Alborghetti

Reviewers

Robert Stupp

• Created: 30/Aug/16 08:46
• Updated: 16/Apr/19 09:30
• Resolved: 01/Sep/16 02:11

Description

Whilst debugging CASSANDRA-12457, I noticed that if we don't stop compactions when draining the 2.2 node, then we may fail to restart the node after upgrading to 3.0.

This is because sstable names in 2.2 have been changed from la to lb but LEGACY_TMP_REGEX_STR in Descriptor.java doe not match lb sstables and therefore it won't clean or ignore temporary files.