I'm also experiencing the flow control to be unhelpful using spring-amqp libraries. Is there a way to just turn it off?
Thanks, Pablo On Fri, May 25, 2012 at 2:57 PM, Chip Salzenberg <[email protected]>wrote: > The fundamental paradox of per-connection flow control is that it holds up > the stop sign just when progress becomes possible. It is backwards and > unhelpful. Consider: > > 1. A client is publishing 1.5K/sec to each of four exchanges, each of > which has a queue. > 2. There are no consumers. Therefore the queue is growing. > 3. RMQ does not stop this. "Flow control" does not trigger. > 4. The consumers appear to begin to tear down the backlog. > 5. RMQ per-connection flow control suddenly decides that now there are > some consumers, now it has a reason to throttle the sender. > 6. If the consumers had not shown up, the producer would not have been > blocked. > > Therefore, it is only when the backlog can go DOWN that the broker decides > to throttle the sender. Not when the backlog was GROWING, but when it > could be SHRINKING, that's when RMQ decides to stop accepting. > > This is not acceptable. > > _______________________________________________ > rabbitmq-discuss mailing list > [email protected] > https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss > > -- You received this message because you are subscribed to the Google Groups "rabbitmq-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rabbitmq-discuss?hl=en.
