Yongle Zhang created CASSANDRA-16291:
----------------------------------------

             Summary: nodes failed to start because of ConfigurationException 
during upgrade C* from 2.2 to 3.0
                 Key: CASSANDRA-16291
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16291
             Project: Cassandra
          Issue Type: Bug
            Reporter: Yongle Zhang


 

Error message:
{code:java}
ERROR 21:57:59 Fatal exception during initialization
org.apache.cassandra.exceptions.ConfigurationException: Found system keyspace 
files, but they couldn't be loaded!
        at 
org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:953) 
~[main/:na]
        at 
org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:407) 
~[main/:na]
        at 
org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:120) 
~[main/:na]
        at 
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:199) 
[main/:na]
        at 
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:607) 
[main/:na]
        at 
org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:774) 
[main/:na]
{code}
 

Reproduce steps: 
 # Start up a cluster of version 2.2 with 10 nodes and one seed
 # Use the stress test tool to generate some data. e.g., 

/cassandra/tools/bin/cassandra-stress write n=1000000 -node 252.11.1.2
 # Stop all nodes, and started the C* nodes running C* compiled from 3.0

5. After upgrading, some of the nodes failed to start because of the 
ConfigurationException.

 



--
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

Reply via email to