cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
Date Wed, 31 May 2017 07:23:05 GMT


Stefania commented on CASSANDRA-13559:

Here are the patches for 3.0 and 3.11:

[patch for 3.0|]
[patch for 3.11|]

Since we don't need it for 4.0, I decided to keep the initial patch suggested by [~jay.zhuang],
I merely added some comments and the entry into CHANGES.txt. I'm running the tests for 3.0
on our internal CI hosts. I will post a comment when the results are available.

Regarding the upgrade from 3.0.13 to 3.0.14, I don't think there is much we can do without
a bump in the messaging version. I would tend to think we should release 3.0.14 with the patch
asap. I also wonder why we did not notice this at all in our [upgrade tests|].

For 3.11 we definitely need the patch since we haven't released it yet; whilst for 4.0 we
don't need it because the messaging version has been bumped and hence the schema version will
not be compared.

Regarding the `NoSuchFieldError` in the ticket description, it doesn't make much sense to
me and I cannot reproduce it. The node starts without problems, perhaps a build issue? 

> Schema version id mismatch while upgrading to 3.0.13
> ----------------------------------------------------
>                 Key: CASSANDRA-13559
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Jay Zhuang
>            Assignee: Stefania
>            Priority: Blocker
> As the order of SchemaKeyspace is changed ([6991556 |],
CASSANDRA-12213), the result of function [{{calculateSchemaDigest}}|]
is also changed for the same schema. Which causes schema mismatch while upgrading 3.0.x ->
> It could cause cassandra fail to start because Unknown CF exception. And streaming will
> {noformat}
> ERROR [main] 2017-05-26 18:58:57,572 - 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
- 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>(
>         at org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.<init>(
>         at org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.<clinit>(
>         at org.apache.cassandra.cql3.QueryProcessor.internalQueryState(
>         at org.apache.cassandra.cql3.QueryProcessor.prepareInternal(
>         at org.apache.cassandra.cql3.QueryProcessor.executeInternal(
>         at org.apache.cassandra.db.SystemKeyspace.checkHealth(
>         at org.apache.cassandra.service.StartupChecks$9.execute(
>         at org.apache.cassandra.service.StartupChecks.verify(
>         at org.apache.cassandra.service.CassandraDaemon.setup(
>         at org.apache.cassandra.service.CassandraDaemon.activate(
>         at org.apache.cassandra.service.CassandraDaemon.main(
> {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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message