[CASSANDRA-15830] Invalid version value: 4.0~alpha4 during startup

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.0-beta1, 4.0
• Component/s: Build, Packaging
• Bug Category: Correctness - API / Semantic Implementation
• Severity: Critical
• Complexity: Low Hanging Fruit
• Discovered By: User Report
• Platform: Linux
• Since Version: 4.0-alpha1

Source Control Link

https://github.com/apache/cassandra/commit/ec1808a34f9aa5ae0b956c1527828566f4ba2be5

Test and Documentation Plan

CASSANDRA-15830

• Assignee: Michael Semb Wever
• Reporter: Eric Wong

Authors

Michael Semb Wever

Reviewers

Benjamin Lerer

• Created: 22/May/20 08:49
• Updated: 16/Jul/20 09:25
• Resolved: 29/May/20 13:20

Description

Hi:

We are testing the latest cassandra-4.0 on Centos 7 using a clean database.  When we started cassandra the first time, everything is fine.  However, when we stop and restart cassandra, we got the following error and the db refuses to startup:

ERROR [main] 2020-05-22 05:58:18,698 CassandraDaemon.java:789 - Exception encountered during startup
java.lang.IllegalArgumentException: Invalid version value: 4.0~alpha4
 at org.apache.cassandra.utils.CassandraVersion.<init>(CassandraVersion.java:64)
 at org.apache.cassandra.io.sstable.SSTableHeaderFix.fixNonFrozenUDTIfUpgradeFrom30(SSTableHeaderFix.java:84)
 at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:250)
 at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:650)
 at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:767)

The only way to get the node up and running again is by deleting all data under /var/lib/cassandra.

 

Is that a known issue?

Thanks, Eric

 

 

 

Issue Links

• is duplicated by: CASSANDRA-15951 Invalid version value: 4.0~alpha4