Draft
Conversation
Contributor
Author
|
Example of a failure like that https://github.com/rabbitmq/rabbitmq-server/actions/runs/22133290092/job/63978468826?pr=14825 |
dumbbell
reviewed
Feb 18, 2026
| "Mnesia protocol negotiation with node ~tp " | ||
| "failed: ~tp. No retries left.", | ||
| [Node, Reason]), | ||
| [] |
Collaborator
There was a problem hiding this comment.
Returning an empty list instead of raising an exception. Is this change of behaviour ok?
Contributor
Author
There was a problem hiding this comment.
I think it is. An empty list is handled as an error in check_mnesia_consistency
Occasionally, clustering will fail with the log
as pasted before. I believe it's because of the parallel
node startup, sometimes leading to crashes.
Hopefully, with retries, we'll handle this more gracefully.
```
Feature flags: nodes `rmq-ct-cluster_size_3_2-2-21072@localhost` and `rmq-ct-cluster_size_3_2-1-21000@localhost` are compatible
Mnesia('rmq-ct-cluster_size_3_2-2-21072@localhost'): ** ERROR ** (ignoring core) ** FATAL ** mnesia_monitor crashed:
{{badmatch, <0.203.0>, Ref<0.1988436133.884998146.137464>}},
{mnesia_monitor, handle_info, 2, [{file, "mnesia_monitor.erl"}, {line, 583}]},
gen_server, try_handle_info, 3, [{file, "gen_server.erl"}, {line, 2434}]},
gen_server, handle_msg, 3, [{file, "gen_server.erl"}, {line, 2420}]},
proc_lib, init_p_do_apply, 3, [{file, "proc_lib.erl"}, {line, 333}]}]}
Error in process <0.300.0> on node 'rmq-ct-cluster_size_3_2-2-21072@localhost' with exit value:
{badarg,[{erlang,send,
[mnesia_locker,{release_tid,{tid,142,<24815.431.0>}}],
[{error_info,#{module => erl_erts_errors}}]},
{mnesia_locker,release_tid,1,[{file,"mnesia_locker.erl"},{line,128}]},
{mnesia_tm,commit_participant,7,
[{file,"mnesia_tm.erl"},{line,1828}]}]}
Application mnesia exited with reason: stopped
BOOT FAILED
===========
Exception during startup:
Exit:{killed,{gen_server,call,[<0.280.0>,{negotiate_protocol,['rmq-ct-cluster_size_3_2-1-21000@localhost']},infinity]}}
gen_server:call/3, line 1301
mnesia_monitor:call/1, line 232
rabbit_mnesia:-check_mnesia_consistency/2-fun-0-/2, line 1002
rabbit_mnesia:with_running_or_clean_mnesia/1, line 1036
rabbit_mnesia:check_cluster_consistency/2, line 719
lists:foldl/3, line 2466
rabbit_mnesia:check_cluster_consistency/0, line 680
rabbit_prelaunch_cluster:setup/1, line 27
```
50cae13 to
02fb19c
Compare
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
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.
Occasionally, clustering will fail with the log
as pasted before. I believe it's because of the parallel node startup, sometimes leading to crashes.
Hopefully, with retries, we'll handle this more gracefully.