Journal.jif prevents RabbitMQ from starting #5197
Unanswered
markusgust
asked this question in
Questions
Replies: 2 comments 3 replies
-
We see this error a few times a year, less and less frequently. Please switch to at least CQv2, or a combination of CQv2, quorum queues and streams. There won't be much time invested into CQv1. In 3.11, all improvements will go into CQv2 and its unification with lazy mode. It likely will become the new default storage option for classic queues. |
Beta Was this translation helpful? Give feedback.
3 replies
-
For anyone seeing this thread, this comment can be helpful: #7203 (comment) Update Apr 21 2023: also see this bug: #7904 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi team,
On a few occasions during the past couple weeks we’ve observed clusters that recently upgraded to 3.10.x sees RabbitMQ crash, restart and attempts to rebuild indices from scratch. We haven't seen a consistent crash reasons, but have attached two examples below. During this rebuild an error occurs which points to a journal.jif file inside mnesia and rabbitMQ refuses to start. When removing either this file or the corrupt .idx file in the queue, rabbitMQ starts again.
We haven’t been able to reproduce this internally. Interestingly, it will mention the last message to
rabbit_classic_queue_index_v2.11
, however neither of the clusters are using CQv2.Below are two examples of where this occurred. Any ideas on what could be causing this?
Example 1:
Example 2:
Happy to provide more info if required.
Beta Was this translation helpful? Give feedback.
All reactions