[CASSANDRA-8049] Explicitly examine current C* state on startup to detect incompatibilities before upgrade

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.2.0 beta 1
• Component/s: Local/Startup and Shutdown
• Severity: Normal
• Assignee: Sam Tunnicliffe
• Reporter: Aleksey Yeschenko

Authors

Sam Tunnicliffe

Reviewers

Aleksey Yeschenko

• Created: 03/Oct/14 15:53
• Updated: 16/Apr/19 09:31
• Resolved: 06/May/15 10:07

Description

Unfortunately, we cannot rely on users reading, and following, NEWS.txt before upgrading. People don't read, or ignore it, and sometimes have issues as the result (see CASSANDRA-8047, for example, and I know of several cases like that one).

We should add an explicit compatibility check on startup, before we modify anything, or write out sstables with the new format. We should fail and complain loudly if we detect a skipped upgrade step.

We should also snapshot the schema tables before attempting any conversions (since it's not uncommon to make schema modifications as part of the upgrade).

Issue Links

• is duplicated by: CASSANDRA-8047 Node refuses to start when 1.2 sstables are present in 2.1