[rabbitmq-discuss] Shovel stops receiving acks from cluster

Jon Bergli Heier jon.bergli.heier at zisson.no
Thu Aug 16 10:13:59 BST 2012


> OK, so if I understand correctly after you restart rabbit1 or rabbit2 the shovel
> plugin stops sending ack after consuming from the source queue, right?

Yes, that seems to be the case.

> Mhm.  Again, what does the shovel status show?  The logs would be useful as
> well.

The shovel status still shows as running on this point. I checked the logs and
couldn't find anything (I have no idea exactly when the shovel disconnects).

I have attached the logs in case they might be of help.

________________________________________
From: rabbitmq-discuss-bounces at lists.rabbitmq.com [rabbitmq-discuss-bounces at lists.rabbitmq.com] on behalf of Francesco Mazzoli [francesco at rabbitmq.com]
Sent: Wednesday, August 15, 2012 19:01
To: Discussions about RabbitMQ
Subject: Re: [rabbitmq-discuss] Shovel stops receiving acks from cluster

Hi Jon,

At Wed, 15 Aug 2012 14:00:54 +0000,
Jon Bergli Heier wrote:
> This is the shovel config on the broker (with credentials and hostnames
> replaced).  The broker nodes in destination are the cluster nodes, and source
> is the local broker I'm shoveling messages from.
>
> [...]
>
> The problem appears when I shut down and then start rabbit1 or rabbit2 (using
> either the debian init script or rabbitmqctl stop_app). All servers are VMs,
> and I've also reproduced this problem by forcing a shutdown of the VM and then
> booting it up again.
>
> I've checked the shovel status in the management interface and it always shows
> as "running" even when the problem appears.

OK, so if I understand correctly after you restart rabbit1 or rabbit2 the shovel
plugin stops sending ack after consuming from the source queue, right?

> On a related note, when letting the broker sit idle for a while (approx. 24
> hours by now) the shovel seems to disconnect from the destination without
> reconnecting even with messages still in the source queue (all of them shows
> as "ready" with none "unacked").

Mhm.  Again, what does the shovel status show?  The logs would be useful as
well.

--
Francesco * Often in error, never in doubt
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss at lists.rabbitmq.com
https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rabbit.log.gz
Type: application/x-gzip
Size: 18737 bytes
Desc: rabbit.log.gz
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120816/195f03e3/attachment.bin>


More information about the rabbitmq-discuss mailing list