[rabbitmq-discuss] Producers hanging when reaching high memory watermark on 1.8.1

Matthias Radestock matthias at rabbitmq.com
Mon Aug 16 10:28:29 BST 2010


On 16/08/10 10:10, Alister Morton wrote:
>> So this then becomes a question of deciding when publishing is "too
>> slow", and being able to continue
> I think conceptually it's different - it's a matter of is the broker
> running "normally" albeit really slowly (that's ok, we'll live with
> it) or has the broker said "Enough!" and sent a flow control message.
> That ought to be a detectable condition, and is fundamentally
> different to a broker simply crawling to a halt.

RabbitMQ could gradually decrease its message acceptance rate as memory 
gets tighter. To the point when just before it reaches the memory 
threshold it, say, is only accepting messages at a rate of 0.01Hz. And 
then, finally, it stops accepting messages altogether. Is that last, 
minuscule change fundamentally different? I don't think so.

Also, from an application's point of view, what would an app do 
differently in response to the broker (or network) running, really, 
really, slowly vs not accepting messages at all? In both cases it is 
left holding the baby, er, message, i.e. it cannot get rid of it by 
placing it on the network stack.



More information about the rabbitmq-discuss mailing list