cassandra-commits mailing list archives

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

    [ https://issues.apache.org/jira/browse/CASSANDRA-11371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15200011#comment-15200011
] 

Aleksey Yeschenko commented on CASSANDRA-11371:
-----------------------------------------------

[~rushman] This is unfortunate but solvable in 3.0 if you have your CQL schema. Try this on
staging first, though.

First, you'll need to wipe all your schema from all the nodes.

On top of clean-slate schema, you'll need to recreate all the keyspaces/tables/types. The
tricky part is preserving the original table ids (post CASSANDRA-5202).

Luckily you can specify id in {{CREATE TABLE}} now with {{CREATE TABLE WITH id = <uuid>}}
syntax. The uuids themselves you can infer from directory names of each table affected.

> Error on startup: keyspace not found in the schema definitions keyspace
> -----------------------------------------------------------------------
>
>                 Key: CASSANDRA-11371
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11371
>             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 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 how to fix this and restart my cluster will be appreciated.



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

Mime
View raw message