cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-11371) Error on startup: keyspace not found in the schema definitions keyspace
Date Thu, 17 Mar 2016 17:45:33 GMT


Aleksey Yeschenko commented on CASSANDRA-11371:

As for Cassandra itself, there isn't much we can do automatically when corruption is introduced.
Make sure you backup your system sstables regularly so that you can just restore them easily
in case something like this ever happens again.

> Error on startup: keyspace not found in the schema definitions keyspace
> -----------------------------------------------------------------------
>                 Key: CASSANDRA-11371
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: Ubuntu
>            Reporter: Sergey Kirillov
>            Assignee: Aleksey Yeschenko
>            Priority: Critical
> My entire cluster is down now and all nodes failing to start with following error:
> {quote}
> ERROR [main] 2016-03-17 15:26:37,755 - Exception encountered
during startup
> java.lang.RuntimeException: sempi_kitkat: not found in the schema definitions keyspace.
>         at org.apache.cassandra.schema.SchemaKeyspace.fetchTable(
>         at org.apache.cassandra.schema.SchemaKeyspace.fetchTables(
>         at org.apache.cassandra.schema.SchemaKeyspace.fetchKeyspace(
>         at org.apache.cassandra.schema.SchemaKeyspace.fetchKeyspacesWithout(
>         at org.apache.cassandra.schema.SchemaKeyspace.fetchNonSystemKeyspaces(
>         at org.apache.cassandra.config.Schema.loadFromDisk( ~[apache-cassandra-3.0.4.jar:3.0.4]
>         at org.apache.cassandra.config.Schema.loadFromDisk( ~[apache-cassandra-3.0.4.jar:3.0.4]
>         at org.apache.cassandra.service.CassandraDaemon.setup(
>         at org.apache.cassandra.service.CassandraDaemon.activate(
>         at org.apache.cassandra.service.CassandraDaemon.main(
> {quote}
> It looks like it is somehow related to CASSANDRA-10964 but I'm using default memtable_allocation_type
> Any advice how to fix this and restart my cluster will be appreciated.

This message was sent by Atlassian JIRA

View raw message