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 3103FDB0B for ; Sat, 20 Oct 2012 02:04:13 +0000 (UTC) Received: (qmail 88769 invoked by uid 500); 20 Oct 2012 02:04:13 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 88747 invoked by uid 500); 20 Oct 2012 02:04:13 -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 88547 invoked by uid 99); 20 Oct 2012 02:04:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 20 Oct 2012 02:04:12 +0000 Date: Sat, 20 Oct 2012 02:04:12 +0000 (UTC) From: "Pavel Yaskevich (JIRA)" To: commits@cassandra.apache.org Message-ID: <1133904212.4364.1350698652848.JavaMail.jiratomcat@arcas> In-Reply-To: <864709175.2205.1350672552073.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (CASSANDRA-4837) IllegalStateException when upgrading schema 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-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13480596#comment-13480596 ] Pavel Yaskevich commented on CASSANDRA-4837: -------------------------------------------- Try following - stop that node, delete all files in schema_*, start the node with disabled gossip, re-create schema using CLI and reintroduce node to the ring. > IllegalStateException when upgrading schema > ------------------------------------------- > > Key: CASSANDRA-4837 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4837 > Project: Cassandra > Issue Type: Bug > Components: Core > Affects Versions: 1.1.6 > Environment: Linux > Reporter: Wade Simmons > Assignee: Pavel Yaskevich > > I am upgrading a cluster from 1.1.2 to 1.1.6. When restarting a node with new code, I am seeing this exception repeat in the logs: > {code} > ERROR [InternalResponseStage:21] 2012-10-19 00:41:26,794 AbstractCassandraDaemon.java (line 135) Exception in thread Thread[InternalResponseStage:21,5,main] > java.lang.IllegalStateException: One row required, 0 found > at org.apache.cassandra.cql3.UntypedResultSet.one(UntypedResultSet.java:50) > at org.apache.cassandra.config.KSMetaData.fromSchema(KSMetaData.java:258) > at org.apache.cassandra.db.DefsTable.mergeKeyspaces(DefsTable.java:406) > at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:355) > at org.apache.cassandra.db.DefsTable.mergeRemoteSchema(DefsTable.java:329) > at org.apache.cassandra.service.MigrationManager$MigrationTask$1.response(MigrationManager.java:449) > at org.apache.cassandra.net.ResponseVerbHandler.doVerb(ResponseVerbHandler.java:45) > at org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:59) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > {code} > I added in some debugging logging to see what Row it was trying to load, and I see this: > {code} > Unable to load keyspace schema: Row(key=DecoratedKey(112573196966143652100562749464385838776, 5365676d656e7473496e746567726174696f6e54657374), cf=ColumnFamily(schema_keyspaces -deleted at 1350665377628000- [])) > {code} > The hex key translates to a schema that exists in schema_keyspaces when I query on the rest of the cluster. I tried restarting one of the other nodes without upgrading the jar and it restarted without exceptions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira