[rabbitmq-discuss] flow control blocked producers vs consumers

asternb at gmail.com asternb at gmail.com
Thu Aug 1 18:42:36 BST 2013

Are you sharing one connection between producers and consumers? You would 
need a separate connection (not just a different channel) for consumers in 
order for them to continue working when flow control blocks the producer's 
connection. Because if you are sharing one connection, blocking the 
producer's connection would also block consumers using that connection, I 

On Friday, July 26, 2013 3:33:09 AM UTC-7, Kobi Biton wrote:
> our rabbitmq (3.0.1) servers blocks producers (logstash) due to flow 
> control triggering (reason is flow on rabbitctl) this however also blocked 
> our consumers , to mitigate it we are restarting the blocked producers and 
> consumers then the queue start to get balanced.
> Reading the flow control docs , how can we avoid from blocking the 
> consumers connections ? can they operate on a different channel ? we also 
> lowered the message TTL and that seemed to slow down the waiting messages, 
> we do understand that we have a bottleneck somewhere along the pipe that 
> said could we configure out consumers to avoid flow control blocking ?
> Kobi  
> 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130801/b4344a66/attachment.htm>

More information about the rabbitmq-discuss mailing list