[
https://issues.apache.org/jira/browse/CASSANDRA-16320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17249890#comment-17249890
]
Yazal Ulloa edited comment on CASSANDRA-16320 at 12/15/20, 7:33 PM:
--------------------------------------------------------------------
[~blerer] I could't run the queries since the nodes couldn't start at all.
I manage to "fix" my problem, I moved the data folder somewhere else (for all
nodes) , create my schema again (with my new changes), use sstableloader to
load the sstables from the old data folder. The materialized view and the
primary table that had the problem where completely corrupted I couldn't
recover that data, but luckily the data from that table was spread out in other
tables. In other tables several fields were corrupted too, all of them were
UDTs, luckily the data was spread in other tables too.
Any idea on how I could get a better solution for this problem?
was (Author: yazalulloa):
[~blerer] I could't run the queries since the nodes couldn't start at all. I
had to move the data folder somewhere else
> Cassandra fails to start after schema changed
> ---------------------------------------------
>
> Key: CASSANDRA-16320
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16320
> Project: Cassandra
> Issue Type: Bug
> Reporter: Yazal Ulloa
> Priority: Normal
>
> I'm using Cassandra 3.11.6 on Centos 7 with a 3 node cluster, I ran some
> schema changes, drop tables/materialized views, alter tables, etc, after that
> one of the materialized views was failing with this error:
> org.apache.cassandra.schema.SchemaKeyspace$MissingColumns: No partition key
> columns found in schema table for my_keyspace.my_materialized_view.
>
> I wanted to replace that materialized view with a table, with the same name
> though, that might be why it's failing
>
> I ran nodetool describecluster and found the schema version was different, I
> tried to run a repair, it didn't work, I restarted the nodes, but they didn't
> start.
> This is the error that is showing up in cassandra.log
>
> ERROR [main] 2020-12-09 10:13:15,827 SchemaKeyspace.java:1017 - No partition
> columns found for table my_keyspace.my_materialized_view in
> system_schema.columns. This may be due to corruption or concurrent dropping
> and altering of a table. If this table is supposed to be dropped, run the
> following query to cleanup: "DELETE FROM system_schema.tables WHERE
> keyspace_name = 'my_keyspace' AND table_name = 'my_materialized_view'; DELETE
> FROM system_schema.columns WHERE keyspace_name = 'my_keyspace' AND table_name
> = 'my_materialized_view';" If the table is not supposed to be dropped,
> restore system_schema.columns sstables from backups.
> org.apache.cassandra.schema.SchemaKeyspace$MissingColumns: No partition key
> columns found in schema table for my_keyspace.my_materialized_view
> at
> org.apache.cassandra.schema.SchemaKeyspace.fetchColumns(SchemaKeyspace.java:1106)
> [apache-cassandra-3.11.6.jar:3.11.6]
> at
> org.apache.cassandra.schema.SchemaKeyspace.fetchTable(SchemaKeyspace.java:1046)
> [apache-cassandra-3.11.6.jar:3.11.6]
> at
> org.apache.cassandra.schema.SchemaKeyspace.fetchTables(SchemaKeyspace.java:1000)
> [apache-cassandra-3.11.6.jar:3.11.6]
> at
> org.apache.cassandra.schema.SchemaKeyspace.fetchKeyspace(SchemaKeyspace.java:959)
> [apache-cassandra-3.11.6.jar:3.11.6]
> at
> org.apache.cassandra.schema.SchemaKeyspace.fetchKeyspacesWithout(SchemaKeyspace.java:936)
> [apache-cassandra-3.11.6.jar:3.11.6]
> at
> org.apache.cassandra.schema.SchemaKeyspace.fetchNonSystemKeyspaces(SchemaKeyspace.java:924)
> [apache-cassandra-3.11.6.jar:3.11.6]
> at org.apache.cassandra.config.Schema.loadFromDisk(Schema.java:92)
> [apache-cassandra-3.11.6.jar:3.11.6]
> at org.apache.cassandra.config.Schema.loadFromDisk(Schema.java:82)
> [apache-cassandra-3.11.6.jar:3.11.6]
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:269)
> [apache-cassandra-3.11.6.jar:3.11.6]
> at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:630)
> [apache-cassandra-3.11.6.jar:3.11.6]
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:757)
> [apache-cassandra-3.11.6.jar:3.11.6]
>
> I tried starting Cassandra with
> -Dcassandra.ignore_corrupted_schema_tables=true and it doesn't work.
>
> Is there a way to fix this?
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]