[rabbitmq-discuss] Shovel stops receiving acks from cluster

Wed Aug 22 17:04:37 BST 2012

Hi,

> So it looks like there is a lot more going on in your system then you
> have hitherto told us about.

Yes, apologies for that.

> Is there any chance you could trim this setup down to the bare
> essentials to help in tracking down the problem?

I just set up two new VMs with RabbitMQ and clustered them. I was still
able to reproduce the problem, but compared to one or two tries it took
me 12 tries (of stopping and starting nodes). I also tried disabling the other
shovels on the shovel node (by commenting them out in the config) and removing
all other queues and exchanges, with that it took 15 tries.

I attached the results of the same commands with the new setup, qa-test1 and
qa-test2 are the new nodes I set up. qa-test1 was the trigger in both cases.

> Also, which node did you bounce - rabbit1 or rabbit2?

rabbit2

Jon
________________________________________
From: Matthias Radestock [matthias at rabbitmq.com]
Sent: Wednesday, August 22, 2012 15:52
To: Jon Bergli Heier
Cc: Discussions about RabbitMQ
Subject: Re: [rabbitmq-discuss] Shovel stops receiving acks from cluster

Jon,

On 22/08/12 14:17, Jon Bergli Heier wrote:
> Attached these as log files, rabbit1 is the destination and shovel is the source
> broker where the shovel lives. The direct connection doesn't seem to show up
> from the report command at all, but I can see it in the management interface.

There are a lot of connections from other rabbits to rabbit1, most of
them from version 2.8.5, some from 2.8.1. There are a few 2.8.6
connections. All but two of the connections have a timeout of 10s
whereas your shovel config indicated that the heartbeat is 5 seconds.

So it looks like there is a lot more going on in your system then you
have hitherto told us about.

I can see that there is one channel on rabbit1 with 1000 pending
confirms, which is certainly odd.

Is there any chance you could trim this setup down to the bare
essentials to help in tracking down the problem?

Also, which node did you bounce - rabbit1 or rabbit2?

Regards,

Matthias.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logs.tar.gz
Type: application/x-gzip
Size: 5273 bytes
Desc: logs.tar.gz
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120822/9ddf2841/attachment.bin>