[
https://issues.apache.org/jira/browse/CASSANDRA-16387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-16387:
----------------------------------------
Test and Documentation Plan: The ultimate goal here is for the upgrade
tests that indicated the problem in the first place to pass consistently. It
should be easy enough to modify the CircleCI config to pull the right branches
from the previous versions...
Status: Patch Available (was: In Progress)
Given the clean test runs, I'm posting the 3.0 and 3.11 versions of the
solution that avoids globally pushing mutations from the distributed system
keyspace schema changes at startup. (Nodes still passively announce their
schema version.)
While this change appears to consistently fix the problem in local test runs
(3.0 -> trunk in-JVM upgrade tests), the next step would be modifying the
CircleCI config to use my 3.0 and 3.11 branches rather than the base branches
to build dtest JARs.
|[CASSANDRA-16387-3.0|https://github.com/apache/cassandra/pull/885]|[CircleCI|https://app.circleci.com/pipelines/github/maedhroz/cassandra/223/workflows/e60f131d-326e-4241-92d4-f51b9043eb62]|
|[CASSANDRA-16387-3.11|https://github.com/apache/cassandra/pull/886]|[CircleCI|https://app.circleci.com/pipelines/github/maedhroz/cassandra/225/workflows/0bea0ed5-9dd6-4a7e-8cae-3a6c5ea7942d]|
> UpgradeTest sporadically failing on schema updates
> --------------------------------------------------
>
> Key: CASSANDRA-16387
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16387
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
> Reporter: Caleb Rackliffe
> Assignee: Caleb Rackliffe
> Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0-rc
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> We’ve observed {{UpdateTest}} failing during what appears to be a schema
> change:
> https://app.circleci.com/pipelines/github/maedhroz/cassandra/192/workflows/ed5305e6-e4f9-420e-9f0a-6153333746dc/jobs/1068
> It almost looks like the Gossiper can’t find its own endpoint state in the
> endpoint state map, and the failure is not consistent, which might suggest a
> race.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
