Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id ACB4218032 for ; Thu, 17 Mar 2016 17:45:34 +0000 (UTC) Received: (qmail 32319 invoked by uid 500); 17 Mar 2016 17:45:34 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 32260 invoked by uid 500); 17 Mar 2016 17:45:34 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 31910 invoked by uid 99); 17 Mar 2016 17:45:33 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Mar 2016 17:45:33 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id B5DF42C1F61 for ; Thu, 17 Mar 2016 17:45:33 +0000 (UTC) Date: Thu, 17 Mar 2016 17:45:33 +0000 (UTC) From: "Aleksey Yeschenko (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-11371) Error on startup: keyspace not found in the schema definitions keyspace MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-11371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)