[rabbitmq-discuss] flow control blocked producers vs consumers

Emile Joubert emile at rabbitmq.com
Fri Aug 2 15:24:41 BST 2013

On 26/07/13 12:39, Kobi Biton wrote:
> 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.

If publishers and consumers use separate connections then blocking of
publishers due to flow control won't affect consumers directly. Though
if publishers slow down that will eventually slow down consumers too
when queues are empty.

Can you explain what you mean when you say consumers are blocked? Are
there messages available in queues that are not being delivered? It
should be possible to determine the reason for messages not being
delivered if you provide the output of "rabbitmqctl report".


More information about the rabbitmq-discuss mailing list