mck created CASSANDRA-12351:
-------------------------------
Summary: IllegalStateException: empty rows returned when reading
system.schema_keyspaces
Key: CASSANDRA-12351
URL: https://issues.apache.org/jira/browse/CASSANDRA-12351
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 starting.
{noformat}
CassandraDaemon.java:644 - Exception encountered during startup
java.lang.IllegalStateException: One row required, 0 found
at
org.apache.cassandra.cql3.UntypedResultSet$FromResultSet.one(UntypedResultSet.java:77)
~[apache-cassandra-2.2.7.jar:2.2.7-SNAPSHOT]
at
org.apache.cassandra.schema.LegacySchemaTables.createKeyspaceFromSchemaPartition(LegacySchemaTables.java:758)
~[apache-cassandra-2.2.7.jar:2.2.7-SNAPSHOT]
at
org.apache.cassandra.schema.LegacySchemaTables.createKeyspaceFromSchemaPartitions(LegacySchemaTables.java:737)
~[apache-cassandra-2.2.7.jar:2.2.7-SNAPSHOT]
at
org.apache.cassandra.schema.LegacySchemaTables.readSchemaFromSystemTables(LegacySchemaTables.java:219)
~[apache-cassandra-2.2.7.jar:2.2.7-SNAPSHOT]
at org.apache.cassandra.config.Schema.loadFromDisk(Schema.java:117)
~[apache-cassandra-2.2.7.jar:2.2.7-SNAPSHOT]
at org.apache.cassandra.config.Schema.loadFromDisk(Schema.java:107)
~[apache-cassandra-2.2.7.jar:2.2.7-SNAPSHOT]
at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:215)
[apache-cassandra-2.2.7.jar:2.2.7-SNAPSHOT]
at
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:522)
[apache-cassandra-2.2.7.jar:2.2.7-SNAPSHOT]
at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:631)
[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.
I haven't bisected the issue yet, but suspect that this is from
CASSANDRA-11502's patch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
