[ https://issues.apache.org/jira/browse/CASSANDRA-15830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17118111#comment-17118111 ]
Michael Semb Wever commented on CASSANDRA-15830: ------------------------------------------------ Reproduced with {code} cd /tmp wget https://downloads.apache.org/cassandra/redhat/40x/cassandra-4.0~alpha4-1.noarch.rpm rpm2cpio cassandra-4.0\~alpha4-1.noarch.rpm| cpio -idmv jar xvf ./usr/share/cassandra/apache-cassandra-4.0~alpha4.jar org/apache/cassandra/config/version.properties cat org/apache/cassandra/config/version.properties {code} The version used is wrong when building the project artifacts inside the [build-rpms.sh|https://github.com/apache/cassandra-builds/blob/master/docker/build-rpms.sh#L75] script, either the ${deb_release} or $CASSANDRA_VERSION. > 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 > Reporter: Eric Wong > Assignee: Michael Semb Wever > Priority: Normal > > 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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org