cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "mck (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-12351) IllegalStateException: empty rows returned when reading system.schema_keyspaces
Date Tue, 02 Aug 2016 11:38:20 GMT


mck commented on CASSANDRA-12351:

{quote}If the code is /sensitive/ in this way maybe adding some assert statements into CFS
would be a good idea, like
assert cf == null || cf.hasColumns() || cf.isMarkedForDelete(){quote}

I take that back. This code is all over the place. It's a shame that CF can have multiple
states representing the same thing.

I can apply the patch, along with a unit test. But a number of tests in ColumnFamilyStoreTest
needs adjustment.
I can apply a different patch, one that improves {{isEmptySchemaPartition(partition)}}.
Or you [~slebresne] can revert CASSANDRA-11427.

> IllegalStateException: empty rows returned when reading system.schema_keyspaces
> -------------------------------------------------------------------------------
>                 Key: CASSANDRA-12351
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Local Write-Read Paths
>            Reporter: mck
>            Assignee: mck
> After 2.2.6 the following error is thrown during startup, resulting in Cassandra not
> {noformat}
> - Exception encountered during startup
> java.lang.IllegalStateException: One row required, 0 found
> at org.apache.cassandra.cql3.UntypedResultSet$
> at org.apache.cassandra.schema.LegacySchemaTables.createKeyspaceFromSchemaPartition(
> at org.apache.cassandra.schema.LegacySchemaTables.createKeyspaceFromSchemaPartitions(
> at org.apache.cassandra.schema.LegacySchemaTables.readSchemaFromSystemTables(
> at org.apache.cassandra.config.Schema.loadFromDisk( ~[apache-cassandra-2.2.7.jar:2.2.7-SNAPSHOT]
> at org.apache.cassandra.config.Schema.loadFromDisk( ~[apache-cassandra-2.2.7.jar:2.2.7-SNAPSHOT]
> at org.apache.cassandra.service.CassandraDaemon.setup( [apache-cassandra-2.2.7.jar:2.2.7-SNAPSHOT]
> at org.apache.cassandra.service.CassandraDaemon.activate( [apache-cassandra-2.2.7.jar:2.2.7-SNAPSHOT]
> at org.apache.cassandra.service.CassandraDaemon.main( [apache-cassandra-2.2.7.jar:2.2.7-SNAPSHOT]
> {noformat}
> In {{LegacySchemaTables.readSchemaFromSystemTables(..)}} the call to {{getSchemaPartitionsForTable(KEYSPACES)}}
is now (since 2.2.6) returning more rows. The additional rows are empty.
> These rows are coming out of the row iterator post 2.2.6, where they were not in 2.2.6.
> This issue was raised on the mailing list [here|].

This message was sent by Atlassian JIRA

View raw message