Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feature_flags_SUITE: Change clustering seed node in few tests #13232

Merged
merged 1 commit into from
Feb 11, 2025

Conversation

dumbbell
Copy link
Member

Why

Some testcases used to use node 1 as the clustering seed node. With mixed-version testing, it could cause issues because node 1 would start with a new version of Ra compared to node 2 and node 2 could fail to join.

How

By using node 2 as the seed node, node 1 running a newer version of Ra should be able to join because it supports talking to an older version.

[Why]
Some testcases used to use node 1 as the clustering seed node. With
mixed-version testing, it could cause issues because node 1 would start
with a new version of Ra compared to node 2 and node 2 could fail to
join.

[How]
By using node 2 as the seed node, node 1 running a newer version of Ra
should be able to join because it supports talking to an older version.
@dumbbell dumbbell self-assigned this Feb 11, 2025
@dumbbell dumbbell marked this pull request as ready for review February 11, 2025 14:48
@dumbbell dumbbell merged commit 55ae918 into main Feb 11, 2025
270 checks passed
@dumbbell dumbbell deleted the adapt-feature_flags_SUITE-to-khepri-0.17.0 branch February 11, 2025 14:49
michaelklishin pushed a commit that referenced this pull request Feb 12, 2025
…khepri-0.17.0

feature_flags_SUITE: Change clustering seed node in few tests

(cherry picked from commit 55ae918)
@dumbbell dumbbell added this to the 4.1.0 milestone Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant