clustering_recovery_SUITE: Add recover_after_partition_with_leader testcase
#14384
Conversation
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
…testcase [Why] The testcase tries to replicate the steps described in issue #12934. [How] It uses intermediate Erlang nodes between the common_test control node and the RabbitMQ nodes, using `peer` standard_io communication. The goal is to make sure the common_test control node doesn't interfere with the nodes the RabbitMQ nodes can see, despite the blocking of the Erlang distribution connection. So far, I couldn't reproduce the problem reported in #12934. @mkuratczyk couldn't either, so it might have been fixed as a side effect of another change... References #12934.
dumbbell
force-pushed
the
test-issue-12934
branch
from
6b431fc to
4f1c6f0
Compare
mkuratczyk
approved these changes
Aug 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why
The testcase tries to replicate the steps described in issue #12934.
How
It uses intermediate Erlang nodes between the common_test control node and the RabbitMQ nodes, using
peerstandard_io communication. The goal is to make sure the common_test control node doesn't interfere with the nodes the RabbitMQ nodes can see, despite the blocking of the Erlang distribution connection.So far, I couldn't reproduce the problem reported in #12934. @mkuratczyk couldn't either, so it might have been fixed as a side effect of another change...
References #12934.