[rabbitmq-discuss] Flow control behavior

Jason McIntosh mcintoshj at gmail.com
Mon Apr 21 19:07:55 BST 2014

Hrmm, I guess it sorta does.  I thought though, at least, I recall testing
about a year ago, where if a consumer was able to consume at only 15
messages a second, then publishing would be restricted (via flow control)
to 15 messages a second.  While testing today, this doesn't appear to be
the case - that publishing is only restricted by the capacities of the
rabbit server (or cluster) locally.


On Mon, Apr 21, 2014 at 12:45 PM, Michael Klishin <mklishin at gopivotal.com>wrote:

> On 21 April 2014 at 20:45:45, Jason McIntosh (mcintoshj at gmail.com) wrote:
> > > Was there ever a time where flow control was based upon consumer
> > rate not queue rates?
> There is flow control based on various Erlang processes (including queues,
> protocol reader
> and consumers) not keeping up with the messages that are being sent to
> them. This
> flow control is temporary, while resource-based can lead to publishers
> being blocked
> for a longer time (until resource alarms clear).
> Does this answer your question?
> --
> MK
> Software Engineer, Pivotal/RabbitMQ

Jason McIntosh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140421/8dc4e087/attachment.html>

More information about the rabbitmq-discuss mailing list