Karl Mueller created CASSANDRA-8330:
---------------------------------------
Summary: Confusing Message: ConfigurationException: Found system
keyspace files, but they couldn't be loaded!
Key: CASSANDRA-8330
URL: https://issues.apache.org/jira/browse/CASSANDRA-8330
Project: Cassandra
Issue Type: Bug
Environment: cassandra 2.0.10
Reporter: Karl Mueller
Priority: Minor
I restarted a node which was not responding to cqlsh. It produced this error:
INFO [SSTableBatchOpen:3] 2014-11-17 16:36:50,388 SSTableReader.java (line
223) Opening /data2/data-cassandra/system/local/system-local-jb-304 (133 bytes)
INFO [SSTableBatchOpen:2] 2014-11-17 16:36:50,388 SSTableReader.java (line
223) Opening /data2/data-cassandra/system/local/system-local-jb-305 (80 bytes)
INFO [main] 2014-11-17 16:36:50,393 AutoSavingCache.java (line 114) reading
saved cache /data2/cache-cassandra/system-local-KeyCache-b.db
ERROR [main] 2014-11-17 16:36:50,543 CassandraDaemon.java (line 265) 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:554)
at
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:261)
at
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:496)
at
org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:585)
After deleting the cache, I still got this error:
INFO 16:41:43,718 Opening
/data2/data-cassandra/system/local/system-local-jb-304 (133 bytes)
INFO 16:41:43,718 Opening
/data2/data-cassandra/system/local/system-local-jb-305 (80 bytes)
ERROR 16:41:43,877 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:554)
at
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:261)
at
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:496)
at
org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:585)
I think possibly the node had corrupted one of the files due to it being in a
bad state. This would be impossible to replicate, so I don't think the actual
bug is that helpful.
What I did find very confusing was the error message. There's nothing to
indicate what the problem is! Is it a corrupt file? A valid file with bad
information in it? Referencing something that doesn't exist?!
I fixed it by deleting the system keyspace and starting it with its token, but
many people wouldn't know to do that at all.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
