[rabbitmq-discuss] Memory watermark alert not resetting.

[Raviv Pavel]

Makes sense.
I'm trying to reproduce with higher watermark by publishing messages,
consuming them but not acking (this is what happened in production) but
can't get the memory to go above the watermark.
Can you explain or point me to an explanation of Rabbit's memory usage?

Also, When hitting the watermark, the server seems to block the producer on
the socket level, instead of sending a flow control message. Since the .Net
SDK doesn't expose a send timeout, publishing is blocked forever.
Any reason for not exposing such timeout?


Thanks
*--*Raviv
*
*



On Thu, Oct 4, 2012 at 6:17 PM, Simon MacMullen <simon at rabbitmq.com> wrote:

> On 04/10/12 16:57, Raviv Pavel wrote:
>
>> Back to the original problem:
>> 1. I set the watermark very low so I can reach it, effectively  78MB
>>
>
> Ah. Was this what you had done in the first place?
>
>
>  2. server starts with empty queues and memory usage is 66MB
>> 3. I start publishing messages and reach the watermark
>> 4. publisher gets blocked
>> 5. I purge the queue but memory stays the same
>>
>
> When you set the watermark very low, close to the "empty" memory use, it
> is very possible that the memory level will go over and never go under
> again. Caches, lazy instantiation and so on. RabbitMQ is not designed for
> highly constrained memory environments.
>
> Cheers. Simon
>
>
> --
> Simon MacMullen
> RabbitMQ, VMware
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121008/656c98df/attachment.htm>