Sergey Kirillov created CASSANDRA-11371:
-------------------------------------------

             Summary: Error on startup
                 Key: CASSANDRA-11371
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11371
             Project: Cassandra
          Issue Type: Bug
          Components: Core
         Environment: Ubuntu
            Reporter: Sergey Kirillov
            Priority: Critical


My entire cluster is down now and all nodes fails to start with following error:

{quote}
ERROR [main] 2016-03-17 15:26:37,755 CassandraDaemon.java:692 - Exception 
encountered during startup
java.lang.RuntimeException: sempi_kitkat: not found in the schema definitions 
keyspace.
        at 
org.apache.cassandra.schema.SchemaKeyspace.fetchTable(SchemaKeyspace.java:947) 
~[apache-cassandra-3.0.4.jar:3.0.4]
        at 
org.apache.cassandra.schema.SchemaKeyspace.fetchTables(SchemaKeyspace.java:938) 
~[apache-cassandra-3.0.4.jar:3.0.4]
        at 
org.apache.cassandra.schema.SchemaKeyspace.fetchKeyspace(SchemaKeyspace.java:901)
 ~[apache-cassandra-3.0.4.jar:3.0.4]
        at 
org.apache.cassandra.schema.SchemaKeyspace.fetchKeyspacesWithout(SchemaKeyspace.java:878)
 ~[apache-cassandra-3.0.4.jar:3.0.4]
        at 
org.apache.cassandra.schema.SchemaKeyspace.fetchNonSystemKeyspaces(SchemaKeyspace.java:866)
 ~[apache-cassandra-3.0.4.jar:3.0.4]
        at org.apache.cassandra.config.Schema.loadFromDisk(Schema.java:134) 
~[apache-cassandra-3.0.4.jar:3.0.4]
        at org.apache.cassandra.config.Schema.loadFromDisk(Schema.java:124) 
~[apache-cassandra-3.0.4.jar:3.0.4]
        at 
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:229) 
[apache-cassandra-3.0.4.jar:3.0.4]
        at 
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:551) 
[apache-cassandra-3.0.4.jar:3.0.4]
        at 
org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:679) 
[apache-cassandra-3.0.4.jar:3.0.4]
{quote}


It looks like it is somehow related to CASSANDRA-10964 but I'm using default 
memtable_allocation_type now.

Any advice would be appreciated.






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to