[rabbitmq-discuss] flow control blocked producers vs consumers

Kobi Biton kbiton at outbrain.com
Fri Jul 26 12:39:43 BST 2013

Michael thanks for the reply.

Our logstash consumers do use their own connection , we do not use the
same connection for publishing (logstash rabbitmq output) and for
consuming (logstash rabbitmq input) , I was under the impression that
the consumers are blocked due to the fact that when rabbitmq starts to
block producers due to flow rates looking at the logstash consumers
logs I see errors connecting to the broker (connection reset by host)
which implies that the broker rejects the consumers connection this of
course leads us to shaky state where messages are no delivered and the
only workaround we found is capturing the blocked producers list from
rabbitmq_ctl and restarting the logstash agents by looping on all the
blocked producers.


On Fri, Jul 26, 2013 at 2:03 PM, Michael Klishin <mklishin at gopivotal.com> wrote:
> Kobi Biton:
>> Reading the flow control docs , how can we avoid from blocking the consumers connections ? can they operate on a different channel ?
> Connections are blocked when you first publish something, so using a connection that's
> only used for consumers should have the effect you want.
> Logstash rabbitmq output should use its own connection. Can you explain how do you share its connection
> with consumers?
> --
> MK

The above terms reflect a potential business arrangement, are provided solely 
as a basis for further discussion, and are not intended to be and do not 
constitute a legally binding obligation. No legally binding obligations will 
be created, implied, or inferred until an agreement in final form is executed 
in writing by all parties involved.

This email and any attachments hereto may be confidential or privileged. 
 If you received this communication by mistake, please don't forward it to 
anyone else, please erase all copies and attachments, and please let me 
know that it has gone to the wrong person. Thanks.

More information about the rabbitmq-discuss mailing list