[
https://issues.apache.org/jira/browse/CASSANDRA-21149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-21149:
----------------------------------------
Change Category: Quality Assurance
Complexity: Low Hanging Fruit
Fix Version/s: 6.x
Status: Open (was: Triage Needed)
> Make shadow gossip round parameters configurable for testing
> ------------------------------------------------------------
>
> Key: CASSANDRA-21149
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21149
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Cluster/Gossip, Test/dtest/python
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Normal
> Fix For: 6.x
>
>
> When upgrading from 5.0 or earlier, nodes must construct an initial
> ClusterMetadata as part of the process to elect the CMS. To do this, a cut
> down version of the Gossip shadow round is used to discover and collate
> information about peers. When the whole cluster is stopped and upgraded at
> the same time, these gossip rounds can take longer to complete as the
> instances come back up. Rolling upgrades are not affected, but several of the
> python upgrade tests perform non-rolling upgrades and we often see these fail
> in CI as the restarts take longer than the default CCM timeout. This issue is
> to make the parameters of that gossip survey configurable, primarily to speed
> up those upgrade tests.
> If the gossip survey can't be completed, nodes fall back to reconstructing
> ClusterMetadata from state saved in system tables, which is always safe as
> any inconsistency between peers will be caught during the election, and it's
> certainly fine in the affected upgrade tests.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
