Replies: 1 comment
-
|
@lrclim RabbitMQ 3.8 has reached end of life in 2022 and classic mirrored queues have long been deprecated. Two node clusters are explicitly recommended against. Publishers do not communicate with consumers. They communicate with queue leader replicas, then that replica communicates with consumers. Depending on the number of messages "in flight" (received by the node), the partition handling strategy used and failure detection timing, it may sometimes seem like two nodes on two sides of a split are communicating. |
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.
-
When a mirrored cluster consisting of two nodes (N1, N2) enters a network partitioned state, with a publisher (P1) and consumer (C1) connected to N1, and another publisher (P2) and consumer (C2) connected to N2, it is possible for a message published by P1 to be received by C2. Is this behavior considered normal?
Beta Was this translation helpful? Give feedback.
All reactions