cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wade Simmons (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4837) IllegalStateException when upgrading schema
Date Wed, 31 Oct 2012 01:04:13 GMT


Wade Simmons commented on CASSANDRA-4837:

I see the same exception loop when applying the patch to 1.1.6.

What would be different in cassandra-1.1 that could possibly fix it? (this is a staging cluster,
so I would rather not upgrade to an unreleased version if it is just a guess). I don't see
anything that looks related to schema in the diff:
> IllegalStateException when upgrading schema
> -------------------------------------------
>                 Key: CASSANDRA-4837
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.1.6
>         Environment: Linux
>            Reporter: Wade Simmons
>            Assignee: Pavel Yaskevich
>         Attachments: CASSANDRA-4837.patch, schematables.tar.gz
> 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
(line 135) Exception in thread Thread[InternalResponseStage:21,5,main]
> java.lang.IllegalStateException: One row required, 0 found
>         at
>         at org.apache.cassandra.config.KSMetaData.fromSchema(
>         at org.apache.cassandra.db.DefsTable.mergeKeyspaces(
>         at org.apache.cassandra.db.DefsTable.mergeSchema(
>         at org.apache.cassandra.db.DefsTable.mergeRemoteSchema(
>         at org.apache.cassandra.service.MigrationManager$MigrationTask$1.response(
>         at
>         at
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
>         at java.util.concurrent.ThreadPoolExecutor$
>         at
> {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:

View raw message