Cassandra pod Fails to start due to inability to load found system keyspace files

Solution Verified - Updated -

Issue

  • One of the cassandra pod fails to come up. we see the following error in the logs:
ERROR [main] <DATE_TIME> CassandraDaemon.java:710 - 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:912) ~[apache-cassandra-3.0.15.redhat-1.jar:3.0.15.redhat-1]
        at org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:362) ~[apache-cassandra-3.0.15.redhat-1.jar:3.0.15.redhat-1]
        at org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:118) ~[apache-cassandra-3.0.15.redhat-1.jar:3.0.15.redhat-1]
        at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) [apache-cassandra-3.0.15.redhat-1.jar:3.0.15.redhat-1]
        at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569) [apache-cassandra-3.0.15.redhat-1.jar:3.0.15.redhat-1]
        at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:697) [apache-cassandra-3.0.15.redhat-1.jar:3.0.15.redhat-1]

Environment

  • Red Hat OpenShift Container Platform
    • 3.9

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In