[rabbitmq-discuss] Unexaplainable behaviour with shovel plugin.
cfautsch at goodgamestudios.com
Mon Mar 31 13:49:52 BST 2014
As promised after some time, here my feedback: We changed the prefetch
count on our shovels to 1000. Since then we observe that our Shovels are
running not nececesarrily faster (not expected) but for sure much more
Two observations we made:
- If no prefetch count is set, and we have a lot of "unacked" Messages,
which are currently residing inside the shovel, a connection loss from the
shovel to the destination broker, can cause the whole source broker to
crash (and all messages are lost if not persisted)
- It seems that messages in "unacked" State in the Source queue cannot be
paged to disk in case of high memory usage.
Thanks again for your advice!
2014-02-27 16:25 GMT+01:00 Claire Fautsch <cfautsch at goodgamestudios.com>:
> Great, Thanks for your valuable comments.
> We will for sure try this out, and I will provide some feedback on the
> 2014-02-27 14:21 GMT+01:00 Simon MacMullen <simon at rabbitmq.com>:
>> On 27/02/14 12:50, Jason McIntosh wrote:
>>> SO I HIGHLY recommend setting a prefetch that's not unlimited if
>>> you're doing WAN replication,
>> So do I. Maybe we should change the default. Hmm.
>> Cheers, Simon
>> Simon MacMullen
>> RabbitMQ, Pivotal
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss