<font face="trebuchet ms,sans-serif">Hi Paul, I haven't dealt with this problem myself as I've never had the need to do so but as far as I know there's no flow control you can put in place between a producer and a consumer. There are similar mechanisms between a producer and the broker (tcp flow control), and between the broker and a consumer (prefetch settings), but nothing built-in for the scenario you describe. </font><div>
<font face="trebuchet ms,sans-serif">What you describe is indeed TCP flow control, but differently from what happens with AMQP, TCP entails a point-to-point connection, so this mechanism makes sense, while it's unlikely that you want a single slow consumer to slow down the entire AMQP broker.<br>
</font><br><div class="gmail_quote">On Tue, Mar 13, 2012 at 23:26, Bell, Paul M. <span dir="ltr"><<a href="mailto:pbell@syncsort.com">pbell@syncsort.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi All,<br>
<br>
What are the Rabbit "best practices" ways of handling a situation where the consumer is v-e-r-y slow and the producer is super-fast. IOW: I am trying to understand the best ways to throttle the producer in such a case. Assume that neither queue nor its topic exchange are durable.<br>
<br>
Can producer obtain information about the state of the queue, e.g., the number of unACKed messages, its size in bytes or number of messages, etc? Or is another approach indicated?<br>
<br>
Thanks very much.<br>
<br>
-Paul<br>
<br>
<br>
<br>
<br>
ATTENTION: -----<br>
<br>
The information contained in this message (including any files transmitted with this message) may contain proprietary, trade secret or other confidential and/or legally privileged information. Any pricing information contained in this message or in any files transmitted with this message is always confidential and cannot be shared with any third parties without prior written approval from Syncsort. This message is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any use, disclosure, copying or distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or Syncsort and destroy all copies of this message in your possession, custody or control.<br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</blockquote></div><br></div>