[rabbitmq-discuss] Re try and Throttling
mark.pork at gmail.com
Wed Mar 9 15:00:33 GMT 2011
What about simulating a delay by not republishing a message back (via
channel.basicReject) onto the queue by the Consumer code? If I'm not
mistaken, as long as the Channel is kept alive, that message can be held out
of the queue indefinitely.
On another note, could a new plugin provide the global delay settings on
Marek Majkowski wrote:
> On Tue, Mar 8, 2011 at 16:08, butterdave2 <mark.pork at gmail.com> wrote:
>> Is there anything in Rabbit that can control the amount of times a
>> may "retry" a message?
> No, but if the message is redelivered you should see "redelivered"
> field being set
> to "True".
>> There may be instances when a message has something about it that will
>> it to "fail" downstream in the Consumer code. I wouldn't want to continue
>> hammer away...
> Correct. But rabbit can't know if your consumer died due to the message
> or due to something else, power failure or something.
> It's the programmers responsibility to handle dying-consumer case.
>> I can programmatically include the number of retry attempts with the
>> (a kind of metadata) and then design the Consumer to query this field.
>> once we hit our MAX_RETRY, we will do something else to it...)
> Sounds good.
>> Also in similar fashion, is there any control around "throttling" or
>> down the consumption of messages from a queue?
> You can't control that, Rabbit is designed to deliver messages when it
> But you can use basic.qos to do something similar. Or, if you're desperate
> you may just run basic.get with regular intervals.
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
View this message in context: http://old.nabble.com/Retry-and-Throttling-tp31098579p31107114.html
Sent from the RabbitMQ mailing list archive at Nabble.com.
More information about the rabbitmq-discuss