[rabbitmq-discuss] RabbitMQ latency and message lost issue.

Marek Majkowski majek04 at gmail.com
Thu Mar 3 12:34:18 GMT 2011

On Wed, Mar 2, 2011 at 13:43, Shixin Song <Shixin.Song at markit.com> wrote:
> To whom it may concern,
> I am testing RabbitMQ at this moment. I have installed rabbitmq server and developed C++ client library using rabbitmq C library.
> I found out that RabbitMQ never drops the message which means it has 0 message loss. But in my case, the latency is much more important than the message loss. Some message loss is acceptable in order to limit the maximal message latency. Could any one inform me how to configure rabbitmq to let it drop some messages when the latency is too high or the queue is reached to a maximum value.

You can tell rabbit to drop messages 'older than' something -

Also take a look at immediate flag to basic.publish (this will forbid
message from
being published if it can't be delivered to a consumer immediately)

But it's your responsibility to ensure that messages are being consumed
fast enough. Queue.ttl and 'immediate' may help, but eventually
RabbitMQ is a queuing system constructed to queue messages - not lose
them randomly.


More information about the rabbitmq-discuss mailing list