[rabbitmq-discuss] erlang-client issue, discarding content?
Suhail Doshi
digitalwarfare at gmail.com
Fri Jul 31 20:33:50 BST 2009
The memory leak is in the consumers, thanks Matthias.
Suhail
On Thu, Jul 30, 2009 at 4:37 PM, Matthias Radestock <matthias at lshift.net>wrote:
> Suhail,
>
> Suhail Doshi wrote:
>
>> Yeah definitely has to be, the moment I kill it the memory drops back down
>> and it is gradually growing, you can even see it gradually growing in the
>> images.
>>
>
> Do you definitely see the rabbit process consuming the memory? How big does
> it get? And what about CPU usage?
>
> The reason I am asking is that killing the server also affects the clients,
> i.e. it is possible that a *client* is consuming all the memory, and
> releases it as soon as the server connection is severed.
>
> So please check the *per-process* memory and CPU stats.
>
> Now, if it really is the server that is eating the memory, please run all
> the various list_* commands in rabbitmqctl to see whether any of them are
> showing growth.
>
> Finally, try publishing messages without marking them as persistent, and
> see whether that changes the behaviour.
>
>
> Regards,
>
> Matthias.
>
--
http://mixpanel.com
Blog: http://blog.mixpanel.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20090731/e6d28556/attachment.htm
More information about the rabbitmq-discuss
mailing list