[rabbitmq-discuss] configure shovel for message throttling

Dushin Fred fred at dushin.net
Fri Jan 25 13:38:22 GMT 2013

As a workaround, you can restart the rabbitmq_shovel OTP application with a new shovels environment, along the lines of something like:

rabbitmqctl eval 'application:stop(rabbitmq_shovel), {ok, [[{rabbit, _}|[{rabbitmq_mochiweb, _}|[{rabbitmq_shovel, [{shovels, Shovels}]}]]]]} = file:consult(".../rabbitmq.config"), application:set_env(rabbitmq_shovel, shovels, Shovels), application:start(rabbitmq_shovel).'

Note that in my case I have complete control over the structure of the rabbitmq.config file, so this solution is not general purpose, but it does work in my limited scenario, and I am sure with a little more creative Erlang you could make the binding to Shovels a bit more resilient...

But the above does not require a restart of the entire broker, or more specifically of the rabbit OTP application.


On Jan 22, 2013, at 6:48 PM, Matthias Radestock <matthias at rabbitmq.com> wrote:

> On 22/01/13 23:41, mabra at manfbraun.de wrote:
>> So I have probably to stay at my start/stop [which is, naturally, not
>> a good pattern ...]. If one adds a new queue, which shovels messages
>> to the next broker [the same, like other, existing queues], one has
>> to adapt these values and start/stop rabbit :-(
> As Simon said yesterday, we do intend to make shovel configuration more dynamic. eventually.
> Matthias.
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

More information about the rabbitmq-discuss mailing list