Replies: 1 comment
-
@njsharpe it means that FYI, classic mirrored queues have been officially deprecated for a couple of years now. Their doc guide warns you that this is a feature to be avoided in the very first paragraph. Classic mirrored queues have known and unfixable failure scenarios that would manifest themselves exactly as you are describing. Please delete and re-declare both as quorum queues. |
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.
-
Hello everyone!
I am new to RabbitMQ and trying to get some queues set up here. I have an exchange (we can call it Ruby), which is attached to two queues; Ruby.Staging and Ruby.Staging.Fault. For whatever reason, Ruby.Staging runs as expected: it's a classic type with durable enabled and the high availability mirroring policy set. However, the Ruby.Staging.Fault is broken in some manner. It shows that durable is enabled, but is does not show any policy, is neither idle or running, and under the messages column it only shows "?" for each sub-column.
I have tried my best to understand what is going on but the short of it is I don't have enough knowledge in this system to figure it out myself. I am all ears, thanks in advance!
System Information
Beta Was this translation helpful? Give feedback.
All reactions