[
https://issues.apache.org/jira/browse/CASSANDRA-19578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17839280#comment-17839280
]
Brandon Williams commented on CASSANDRA-19578:
----------------------------------------------
We'll also need to multiplex SchemaTest for flakiness, which I ram
[here|https://app.circleci.com/pipelines/github/driftx/cassandra/1592/workflows/a84707b9-9ff8-4d49-af26-015a5e99d2b4/jobs/85318/tests]
and is failing, which I verified, and learned that it is only failing when the
suite is run, but testTransKsMigration passes in isolation.
> Concurrent equivalent schema updates lead to unresolved disagreement
> --------------------------------------------------------------------
>
> Key: CASSANDRA-19578
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19578
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Schema
> Reporter: Chris Lohfink
> Priority: Normal
> Fix For: 4.1.5, 5.0-beta2
>
>
> As part of CASSANDRA-17819 a check for empty schema changes was added to the
> updateSchema. This only looks at the _logical_ schema difference of the
> schemas, but the changes made to the system_schema keyspace are the ones that
> actually are involved in the digest.
> If two nodes issue the same CREATE statement the difference from the
> keyspace.diff would be empty but the timestamps on the mutations would be
> different, leading to a pseudo schema disagreement which will never resolve
> until resetlocalschema or nodes being bounced.
> Only impacts 4.1
> test and fix :
> https://github.com/clohfink/cassandra/commit/ba915f839089006ac6d08494ef19dc010bcd6411
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
