You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Michael Semb Wever (Jira)" <ji...@apache.org> on 2020/05/28 21:46:00 UTC
[jira] [Issue Comment Deleted] (CASSANDRA-15830) Invalid version
value: 4.0~alpha4 during startup
[ https://issues.apache.org/jira/browse/CASSANDRA-15830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Semb Wever updated CASSANDRA-15830:
-------------------------------------------
Comment: was deleted
(was: Currently we have no way of testing debian or rpm packaging. This is a problem, it hurts when cutting releases as well as afterwards (like this ticket). I've entered a separate ticket to add testing of debian or rpm packaging.)
> Invalid version value: 4.0~alpha4 during startup
> ------------------------------------------------
>
> Key: CASSANDRA-15830
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15830
> Project: Cassandra
> Issue Type: Bug
> Components: Build, Packaging
> Reporter: Eric Wong
> Assignee: Michael Semb Wever
> Priority: Normal
> Fix For: 4.0-alpha
>
>
> 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:
> {code}
> 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)
> {code}
> 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
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org