[jira] [Commented] (CASSANDRA-11371) Error on startup: keyspace not found in the schema definitions keyspace

2016-03-19 Thread Sergey Kirillov (JIRA)

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

Sergey Kirillov commented on CASSANDRA-11371:
-

It looks like system_schema.tables is damaged and many table names contain 
random binary data. It is disaster. Is there any way to rebuild 
system_schema.tables from existing sstables and CQL schema?

> 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
>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)


[jira] [Commented] (CASSANDRA-11371) Error on startup: keyspace not found in the schema definitions keyspace

2016-03-19 Thread Sergey Kirillov (JIRA)

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

Sergey Kirillov commented on CASSANDRA-11371:
-

Thank you Aleksey. Any advice how to do this in multinode cluster? Do I need to 
do it on every node or on just one and the rest will pick up changes?

> 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)


[jira] [Commented] (CASSANDRA-11371) Error on startup: keyspace not found in the schema definitions keyspace

2016-03-19 Thread Aleksey Yeschenko (JIRA)

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

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: 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)


[jira] [Commented] (CASSANDRA-11371) Error on startup: keyspace not found in the schema definitions keyspace

2016-03-19 Thread Aleksey Yeschenko (JIRA)

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

Aleksey Yeschenko commented on CASSANDRA-11371:
---

[~rushman] Neer to clear it on every node. But it should be enough to run all 
your {{CREATE}} s just once.

> 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)


[jira] [Commented] (CASSANDRA-11371) Error on startup: keyspace not found in the schema definitions keyspace

2016-03-19 Thread Aleksey Yeschenko (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-11371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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 
= }} 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)