[rabbitmq-discuss] RabbitMQ Shovel Connections

[Jelle Smet]

Hi Alex,

Thank you for the detailed feedback.
Meanwhile I have found and fixed some issues on the software making use of 
RabbitMQ.
I made a tool which has a work pool of multiple processes running 
(Python/multiprocessing/Pika).
Under certain circumstances a worker crashes while the connection to the 
broker stays alive, which left the message in a permanent unacknowledged 
state as long the work pool manager stayed alive.
This has been fixed.  I'm afraid this situation has clouded my judgement on 
finding the reason for this behavior.

Here are the relevant portions of version info.  (All brokers run the same 
version)

... snip ...
{erlando,"Syntax extensions for Erlang","2.6.1"},
      {rabbitmq_federation,"RabbitMQ Federation","2.6.1"},
      {rabbitmq_shovel,"Data Shovel for RabbitMQ","2.6.1"},
      {rabbitmq_shovel_management,"Shovel Status","2.6.1"},
      {rabbitmq_management,"RabbitMQ Management Console","2.6.1"},
      {webmachine,"webmachine","1.7.0-rmq2.6.1-hg0c4b60a"},
      {rabbitmq_management_agent,"RabbitMQ Management Agent","2.6.1"},
      {amqp_client,"RabbitMQ AMQP Client","2.6.1"},
      {rabbit,"RabbitMQ","2.6.1"},
      {os_mon,"CPO  CXC 138 46","2.2.6"},
      {sasl,"SASL  CXC 138 11","2.1.9.4"},
      {rabbitmq_mochiweb,"RabbitMQ Mochiweb Embedding","2.6.1"},
      {mochiweb,"MochiMedia Web Server","1.3-rmq2.6.1-git9a53dbd"},
      {inets,"INETS  CXC 138 49","5.6"},
      {mnesia,"MNESIA  CXC 138 12","4.4.19"},
      {stdlib,"ERTS  CXC 138 10","1.17.4"},
      {kernel,"ERTS  CXC 138 10","2.14.4"}]},
... snip ...

I will upgrade my environment to the latest stable version 2.7.0 as this is 
the latest stable release.

since a broker restart
>     will mark the unacknowledged messages as ready again, and deliver
>     them to a consumer.


In my case I was unable to restart the broker, ... it just 
hung indefinitely forcing me to kill the RabbitMQ process.

What I will do is the following:

   - Upgrade all participating RabbitMQ servers to the latest stable 
   version (2.7.0)
   - Try to reproduce the problem.
      - If the problem occurs I provide you detailed and complete 
      information broker configuration (I rather do this offline then)
      - If the problem can't be reproduced, I'll provide feedback on that 
      to this post.
   
Thanks again Alex for the time taken to read through an analyse the 
provided information, much appreciated.


Cheers,

Jelle




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20111114/842513db/attachment.htm>