[rabbitmq-discuss] Shovel terminated status

Matthias Radestock matthias at rabbitmq.com
Wed Aug 22 00:33:36 BST 2012


On 21/08/12 16:45, Elizabeth Liao wrote:
> Questions: In the documentation, it states that the timestamp from  $
> rabbitmqctl eval 'rabbit_shovel_status:status().' is the time when
> shovel entered the state.  I've observed this for the running and
> starting state but not for the terminated state.  The timestamp for
> the terminated state appears to be the current time.

Your config has a reconnect_delay of 1 (second), so when the shovel 
initialisation fails it will attempt to reconnect after one second, 
which puts the shovel in the 'starting' state, fail and go straight back 
to the 'terminated' state. Then one second later the same happens. And 
so on. Hence the moving timestamp.

> Additionally, it seems when a shovel is in the terminated state and
> periodically trying to reconnect, there are many connections left
> open with no active channels.

What exactly are you observing here? The number of connections returned 
by 'rabbitmqctl list_connections' at the broker the shovel is connecting to?

Btw, it would be good if you conducted your testing with the latest 
RabbitMQ version. Makes it easier for us to investigate any problems.



More information about the rabbitmq-discuss mailing list