HCD-241: Add a dedicated DSE 6.9 upgrade test#90
Open
szymon-miezal wants to merge 7 commits intomainfrom
Open
Conversation
szymon-miezal
force-pushed
the
HCD-241
branch
from
29c452e to
6aeadf3
Compare
szymon-miezal
force-pushed
the
HCD-241
branch
from
31a03c5 to
9b4456f
Compare
szymon-miezal
force-pushed
the
HCD-241
branch
from
e0a5501 to
b293de7
Compare
szymon-miezal
commented
Feb 20, 2026
|
|
||
|
|
||
| @flaky(rerun_filter=test_failure_due_to_timeout) | ||
| #@flaky(rerun_filter=test_failure_due_to_timeout) |
szymon-miezal
commented
Feb 20, 2026
| # In case you want to test a patch with your own CCM branch, further to changing below CCM repo and branch name, you need to add -e flag at the beginning | ||
| # Example: -e git+https://github.com/userb/ccm.git@cassandra-17182#egg=ccm | ||
| git+https://github.com/datastax/cassandra-ccm.git@converged-cassandra#egg=ccm | ||
| -e git+https://github.com/datastax/cassandra-ccm.git@HCD-267#egg=ccm |
Author
There was a problem hiding this comment.
TODO: remove once datastax/cassandra-ccm#3 is merged
szymon-miezal
force-pushed
the
HCD-241
branch
from
7db627f to
25fa91b
Compare
szymon-miezal
changed the title
Author
|
Note that 25fa91b is purely experimental, will be dropped before merging. |
bereng
reviewed
Feb 25, 2026
| upgraded_node_3 = self._upgrade_node(cluster, nodes[2], internode_encryption=internode_encryption) | ||
| self._assert_insert_select_works(upgraded_node_3, 300, 400) | ||
|
|
||
| # rolling restart post upgrade |
There was a problem hiding this comment.
This should be explained imo as to why are we doing it. Couldn't all these be just a loop against an array `upgraded_nodes' i.e.?
Author
There was a problem hiding this comment.
Could be, I thought about not polluting the loop with weird usage of index to get different ranges of data to write but I can try it out.
I do agree a comment explaining the motivation for post upgrade restart is a good idea.
bereng
reviewed
Feb 27, 2026
The goal of this patch is to add a distinct upgrade test for DSE 6.9 upgrade path. The test aims at preparing some lightweight data and conduct a rolling upgrade while inserting more data - the goal is to ensure the internode communication does not break when cluster is in a mixed version state. The test consists from encrypted and non-encrypted variant.
Jenkins does not have permissions to checkout from bdp
This reverts commit a2a4490.
| r'Received a read request from .* for a token .* that is not owned by the current replica .* key=cassandra .*' | ||
| r'Received a read request from .* for a token .* that is not owned by the current replica .* key=cassandra .*', | ||
| # the two below error patterns are needed by DSE upgrade tests | ||
| r'that is incompatible with the version this node can handle', |
Member
There was a problem hiding this comment.
fyi, this line addresses (by suppression) HCD-193
https://github.com/riptano/bdp/pull/21617
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The goal of this patch is to add a distinct upgrade test for DSE 6.9 upgrade path.
The test aims at preparing some lightweight data and conduct a rolling upgrade
while inserting more data - the goal is to ensure the internode communication does not
break when cluster is in a mixed version state.
The test consists from encrypted and non-encrypted variant.
Complementary ccm PR: datastax/cassandra-ccm#3
It is a test for datastax/cassandra#2240
How to run the test locally: