You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Andrew O'Connor (JIRA)" <ji...@apache.org> on 2018/05/22 18:23:00 UTC

[jira] [Commented] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13

    [ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16484388#comment-16484388 ] 

Andrew O'Connor commented on CASSANDRA-13559:
---------------------------------------------

Hello everyone. I am seeing this error when restarting a 3.0.12 node.

ERROR [main] 2018-05-22 17:53:09,355 CassandraDaemon.java:710 - Exception encountered during startup
java.lang.IllegalArgumentException: Unknown CF 10c30740-1284-11e8-862f-5f9049872b18
 at org.apache.cassandra.db.Keyspace.getColumnFamilyStore(Keyspace.java:206) ~[apache-cassandra-3.0.12.jar:3.0.12]

I realize this thread is mostly concerned with upgrades. We are not trying to upgrade. Simply trying to stop and then restart the service on a single node in a long running cluster.

Any advice how we can recover this node?

> Schema version id mismatch while upgrading to 3.0.13
> ----------------------------------------------------
>
>                 Key: CASSANDRA-13559
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13559
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Jay Zhuang
>            Assignee: Jay Zhuang
>            Priority: Blocker
>             Fix For: 3.0.14, 3.11.0
>
>
> As the order of SchemaKeyspace is changed ([6991556 | https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], CASSANDRA-12213), the result of function [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] is also changed for the same schema. Which causes schema mismatch while upgrading 3.0.x -> 3.0.13.
> It could cause cassandra fail to start because Unknown CF exception. And streaming will fail:
> {noformat}
> ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception encountered during startup
> java.lang.IllegalArgumentException: Unknown CF 83c8eae0-3a65-11e7-9a27-e17fd11571e3
> {noformat}
> {noformat}
> WARN  [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from socket; closing
> org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this is likely due to the schema not being fully propagated.  Please wait for schema agreement on table creation.
> {noformat}
> Restart the new node will cause:
> {noformat}
> Exception (java.lang.NoSuchFieldError) encountered during startup: ALL
> java.lang.NoSuchFieldError: ALL
>         at org.apache.cassandra.service.ClientState.<clinit>(ClientState.java:67)
>         at org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.<init>(QueryProcessor.java:155)
>         at org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.<clinit>(QueryProcessor.java:149)
>         at org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163)
>         at org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286)
>         at org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294)
>         at org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900)
>         at org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354)
>         at org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110)
>         at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179)
>         at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569)
>         at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:697)
> {noformat}
> I would suggest to have the older list back for digest calculation and release 3.0.14.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org