[rabbitmq-discuss] Unexaplainable behaviour with shovel plugin.

Laing, Michael michael.laing at nytimes.com
Wed Mar 5 17:18:27 GMT 2014

Basically, we delay the ack by adding a timeout/callback to the event loop
after processing a message from the 'silver' queue. The delay reflects the
desired rate. Crude but it works. We use pika w the libev adapter I wrote.

BTW re node restart: we do restart our Cassandra nodes if they fail. They
discover and automatically sync up w the other Cassandra nodes. This has
happened in production. We also do rolling restarts of the production
Cassandra cluster to upgrade to new versions.

On Wed, Mar 5, 2014 at 10:54 AM, Ben Hood <0x6e6562 at gmail.com> wrote:

> On Wed, Mar 5, 2014 at 12:51 PM, Laing, Michael
> <michael.laing at nytimes.com> wrote:
> > Some of our fabrik apps apply flow control. For example, we apply flow
> > control to the ingress of 'silver' service messages so that 'gold'
> service
> > takes precedence.
> How do you apply flow control in your infrastructure?
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140305/32ce5cd6/attachment.html>

More information about the rabbitmq-discuss mailing list