This is an automated email from the ASF dual-hosted git repository.

samt pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra-dtest.git


The following commit(s) were added to refs/heads/trunk by this push:
     new fcaaedb2 Make shadow gossip round fail fast during non-rolling upgrade
fcaaedb2 is described below

commit fcaaedb23ce36f8f89fb3c6feabf40e3bb5396ea
Author: Sam Tunnicliffe <[email protected]>
AuthorDate: Mon Mar 16 18:01:56 2026 +0000

    Make shadow gossip round fail fast during non-rolling upgrade
    
    Patch by Sam Tunnicliffe; reviewed by Marcus Eriksson for
    CASSANDRA-21149
---
 upgrade_tests/upgrade_through_versions_test.py | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/upgrade_tests/upgrade_through_versions_test.py 
b/upgrade_tests/upgrade_through_versions_test.py
index 4f6a1960..2471ed93 100644
--- a/upgrade_tests/upgrade_through_versions_test.py
+++ b/upgrade_tests/upgrade_through_versions_test.py
@@ -579,7 +579,9 @@ class TestUpgrade(Tester):
             # Setup log4j / logback again (necessary moving from 2.0 -> 2.1):
             node.set_log_level("INFO")
             node.start(wait_other_notice=400, wait_for_binary_proto=True,
-                       
jvm_args=['-Dcassandra.disable_max_protocol_auto_override=true'])  # prevent 
protocol capping in mixed version clusters
+                       jvm_args = 
['-Dcassandra.disable_max_protocol_auto_override=true',  # prevent protocol 
capping in mixed version clusters
+                                   
'-Dcassandra.shadow_round_timeout_millis=100'])  # gossip to construct initial 
ClusterMetadata will fail on the
+                                                                               
     # first node as everything is down
             node.nodetool('upgradesstables -a')
 
     def _log_current_ver(self, current_version_meta):


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to