[rabbitmq-discuss] Shovel stops receiving acks from cluster
francesco at rabbitmq.com
Wed Aug 15 18:01:45 BST 2012
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
Francesco * Often in error, never in doubt
More information about the rabbitmq-discuss