[rabbitmq-discuss] load distribution among queue consumers and consumer_tag in non-exclusive mode

Ashok Anand ashok.anand at gmail.com
Sun Jul 7 04:15:12 BST 2013


I see. so tags does not affect delivery. If I have 4 channels reading from
same queue, messages will be distributed across 4 channels.

Another question I had, regarding reading multiple messages. Consider a
distributed WAN deployment situation, where consumer and rabbitmq broker
are 60 ms apart (RTT of 120 ms). If consumer can get only one message from
queue in one read, then it can only get 7-8 messages/second. We can use
multi-threading, but if there is support of reading multiple messages in
one read, that could improve the read rate even in WAN deployment and with
single thread - I was wondering if there is a support for such read or if
there is a plan..


On Sat, Jul 6, 2013 at 12:29 PM, Tim Watson <watson.timothy at gmail.com>wrote:

> Tags uniquely identify consumers in a channel and are used in some methods
> such as basic.cancel. They won't affect delivery and can be duplicated
> across different channels. The server will also allocate them if you do not.
>
> Cheers
> Tim
>
> On 6 Jul 2013, at 06:16, Ashok Anand <ashok.anand at gmail.com> wrote:
>
> > I am looking at message distribution among multiple consumers listening
> to the same queue..   Should these consumers use different consumer tags?
> >
> > I tried with non-exclusive access to the queue with 4 consumers using
> same consumer tag. My question is whether using same consumer tag will give
> predicted behavior - or I must use different consumer tags.
> >
> > I did find that messages get distributed among 4 consumers in
> round-robin manner even using same consumer tag.  Just wondering if this
> happened by chance, and ideally, these consumers must use different
> customer tags? I am not sure about semantics of consumer tags in
> non-exclusive mode access..
> > _______________________________________________
> > rabbitmq-discuss mailing list
> > rabbitmq-discuss at lists.rabbitmq.com
> > https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130707/744917fb/attachment.htm>


More information about the rabbitmq-discuss mailing list