cassandra-commits mailing list archives

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


Stefan Podkowinski commented on CASSANDRA-13559:

There are two different upgrade issues here. Let's not mix those up.

*3.0.x -> 3.0.13*

Based on the description by [~jay.zhuang] for this ticket, any node on  3.0.x that will be
upgraded to the latest 3.0.13 bug fix release, will fail to start. This is the actual point
why pulling the .13 release from the download page is probably a good idea, so people won't
upgrade their cluster just to find themselves in a situation unable to bring any node up again.

*3.0.13 -> 3.0.14 (unrelease)*

Some users may already run 3.0.13 (e.g. by upgrading from 2.x or fresh installs). Maybe even
on large production clusters. If we change the schema digest calculation in .14 again, we
need to make sure that the users on .13 will be able to upgrade to .14 as well without seeing
major issues, e.g. with schema migration storms. 

> 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