[rabbitmq-discuss] Testing Shovel on a WAN

Thu Mar 29 08:28:30 BST 2012

Thank you Simon.

> That seems unlikely. Packet loss should lead to redelivery at the TCP 
> level, which the shovel should be unaware of.

> Messages should only get redelivered if the consumer rejects them or the 
> TCP connection is interrupted completely. Shovel won't reject messages, 
> but maybe the connection is being interrupted and re-established? You 
> should be able to see this in the logs. You would also see a 
> "redelivered" message rate in mgmt.

Where could I get the redelivered messages rate ?
I can't see it in the mngt interface. 
I only have : 
Messages /
	Ready
	Unack
	Total
Messages rate / 
	Incoming
	Deliver / get
	Ack
I also tried with the command : python rabbitmqadmin.py -H <myhost> -f raw_json list queues, and there no redelivered field in the displayed values.

> unacknowledged -> the message has been consumed by the remote end, but 
> not acknowledged.

As the network is cut, the remote end cannot consume messages.
They all stay in the Shovel queue, or somewhere else at the local end. 
Shouldn't they have the Ready Status ?

>
> After 900 seconds presumably the connection is determined to be dead by 
> RabbitMQ and then the messages go back into the queue ("ready").
What do you mean by "go back into the queue" ?
Does-it mean that unacknowledged messages, are no longer in the Shovel Queue ?
Shovel code, reads messages from its queue, and keep them in memory until an ack is received ?
If Yes, what if the broker crashes ? Are we going to lose all unack messages in that case (if we do not use HA queues)?

>
> Then when the network recovers, they are sent again and become 
> "unacknowledged" again, until the acks come in.

Cheers, 
Denis
#
" Ce courriel et les documents qui lui sont joints peuvent contenir des informations confidentielles ou ayant un caractère privé. S'ils ne vous sont pas destinés, nous vous signalons qu'il est strictement interdit de les divulguer, de les reproduire ou d'en utiliser de quelque manière que ce soit le contenu. Si ce message vous a été transmis par erreur, merci d'en informer l'expéditeur et de supprimer immédiatement de votre système informatique ce courriel ainsi que tous les documents qui y sont attachés."
******
" This e-mail and any attached documents may contain confidential or proprietary information. If you are not the intended recipient, you are notified that any dissemination, copying of this e-mail and any attachments thereto or use of their contents by any means whatsoever is strictly prohibited. If you have received this e-mail in error, please advise the sender immediately and delete this e-mail and all attached documents from your computer system."
#