You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Wade Simmons (JIRA)" <ji...@apache.org> on 2012/10/20 00:54:11 UTC
[jira] [Updated] (CASSANDRA-4837) IllegalStateException when
upgrading schema
[ https://issues.apache.org/jira/browse/CASSANDRA-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wade Simmons updated CASSANDRA-4837:
------------------------------------
Description:
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.
was:
I am upgrading a cluster from 1.1.2 to 1.1.6. When restarting the second 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.
> 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