[rabbitmq-discuss] Pathological dead queue behavior in a cluster.
matthew at rabbitmq.com
Wed Mar 30 22:31:13 BST 2011
On Wed, Mar 30, 2011 at 03:26:30PM -0600, Jason J. W. Williams wrote:
> > Actually, if you did a basic.cancel and then a basic.consume then you
> > should find you can start consuming from the queue again. That is the
> > expected strategy in light of the above notification extension.
> Why does the queue count stay at 0 though until the rebind? That wouldn't
> have anything to do with the consumption being re-established no?
Once the queue comes back up, provided the exchange to which it was
bound was _also_ durable, the bindings will be recreated. At that point
new msgs published to the queue should appear in the queue.
As for msgs that were previously sent to the queue before the node died,
a) they could have been consumed and ack'd by the consumer
b) they might not have been published persistent
c) they might have not been sync'd to disk so didn't get recovered
I'm afraid I don't have time right now to check your code to see if any
of these hypothesis hold true.
More information about the rabbitmq-discuss