[
https://issues.apache.org/jira/browse/CASSANDRA-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17205713#comment-17205713
]
Caleb Rackliffe commented on CASSANDRA-16148:
---------------------------------------------
bq. It would be great if we could get a baseline with and without memoize with
a 50-100 node cluster with at least 1 node in 3.x.
Would a microbenchmark hammering {{haveMajorVersion3Nodes()}} over 100
endpoints suffice to allay our fears? (i.e. One comparing trunk to a version of
the patch w/ a {{volatile}} {{haveMajorVersion3Nodes}}?)
> Test failures caused by merging CASSANDRA-15833
> -----------------------------------------------
>
> Key: CASSANDRA-16148
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16148
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Gossip
> Reporter: Jordan West
> Assignee: Jordan West
> Priority: Normal
>
> Three issues were caused by merging CASSANDRA-15833:
> 1. `GossiperTest#testHaveAnyVersion3Nodes` was failing on trunk:
> https://app.circleci.com/pipelines/github/jrwest/cassandra/53/workflows/95f9f401-1ef8-4b8d-9c64-3703d9669d95/jobs/771
> 2. python dtest ReadRepairTest#test_atomic_writes[blocking] was failing
> 3. In-jvm dtests being worked on as part of CASSANDRA-15977 uncovered an
> issue with how CASSANDRA-15833 changes interacted with in-jvm dtests running
> without {{Feature.GOSSIP}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
