cassandra-commits mailing list archives

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


Aleksey Yeschenko commented on CASSANDRA-13559:

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

There is only one confirmed issue here. It's a shame the JIRA is mixed up. We accidentally
changed the way the digest is calculated, slightly, in 3.0.13. The issue is increased migration
traffic. Not a big deal, but we should roll it back, so that the majority (lagging behind
latest, always) is not affected.

bq,  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.

Well, we can't, so you have to choose one:
1. prevent extra migration traffic for those migrating from [3.0.0, 3.0.12] to 3.0.14+
2. prevent extra migration traffic for those migrating from 3.0.13 to 3.0.14+

With 3.0.13 being super fresh, with relatively few people on it (who already went through
some extra migrations and survived anyway), I would say (1) is more important than (2).

> 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