Skip to content

Do not contact disconnected nodes in rabbit_nodes:list_running/0 #10353

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

Merged
merged 4 commits into from
Jan 18, 2024

Conversation

kjnilsson
Copy link
Contributor

As this will force erlang to attempt to set up a distribution connection to the down node. This can take some time, especially in cloud environments.

…ning/1

As this will force erlang to attempt to set up a distribution connection
to the down node. This can take some time, especially in cloud environments.
@kjnilsson kjnilsson requested a review from dumbbell January 17, 2024 11:59
@kjnilsson kjnilsson changed the title Do not contact disconnected nodes in rabbit_nodes:list_running/1 Do not contact disconnected nodes in rabbit_nodes:list_running/0 Jan 17, 2024
@kjnilsson kjnilsson added this to the 3.13.0 milestone Jan 17, 2024
Ram nodes are a deprecated feature and the actual assertion is
quite a complicated once that isn't easy to reason about as it
asserts on the cluster view of nodes that that have their
rabbit app stopped.
@michaelklishin
Copy link
Collaborator

This forced push was a rebase.

@michaelklishin
Copy link
Collaborator

This has reproducible failures in

bt //deps/rabbit:cluster_rename_SUITE

During the clustering step, one node logs

Mnesia: node jessica@localhost thinks it's clustered with node 'rename_cluster_one_by_one-3@localhost', but 'rename_cluster_one_by_one-3@localhost' disagrees

So the implicit connection behavior is important in a few more test suites that actively mess with nodes (kill them, shut them down, rename them).

@michaelklishin
Copy link
Collaborator

To further confirm this, editing out the filtering line on this branch immediately makes the above test suite pass :(

The behaviour of this module is to fragile to potentially allow a regression
here so we explicitly ping_all/0 before filtering running nodes.
@kjnilsson kjnilsson merged commit 85dc3b1 into main Jan 18, 2024
@kjnilsson kjnilsson deleted the list-running-opt branch January 18, 2024 14:36
michaelklishin added a commit that referenced this pull request Jan 18, 2024
michaelklishin added a commit that referenced this pull request Jan 18, 2024
Do not contact disconnected nodes in rabbit_nodes:list_running/0 (backport #10353)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants