[rabbitmq-discuss] Consumer stop to receive messages but continue listening queue problem.

Matthew Sackman matthew at lshift.net
Fri Mar 26 18:11:31 GMT 2010


On Fri, Mar 26, 2010 at 08:33:19AM -0500, Bryan Murphy wrote:
> Another technique we use:
> Start one consumer.
> Start your other consumers.
> Restart the first consumer.
> This let's you keep the high prefetch settings while still getting the
> messages to distribute more evenly.

I would not recommend that at all - you're likely to get messages in
different orders with this scheme. QoS is much better idea, or, use
channel.flow from the client (may only work in newer-than-1.7.2 - can't
remember when it appeared) to prevent any messages being sent out
*before* issuing the basic.consume.

You could then have either a delay or some signal through some other
exchange and queues (and channel) to get the clients to drop the
channel.flow and start consuming.


More information about the rabbitmq-discuss mailing list