Open Stack

It is also a good idea to get hold of queues whose consumers are 0 and have
alot of messages/big in size.
What we have observed in our environment is RabbitMQ starts showing some
slowness @ RES Memory consumption of 3+GB(Note: not Virtual)

Also since RabbitMQ runs inside an Erlang VM its a good Idea to get Stats
out of the same. Stats like say Garbage Collection, Scheduler Usage(Erlang
Scheduler), Runqueue Length etc, alot is explained in
https://github.com/ferd/vmstats/

There are a lot of ways to collect these statistics, by spinning up a
separate erlang VM with the command:
erl -sname <whatever> -setcookie <whatever cookie you are using in your
RabbitMQ cluster>
<Once in erlang shell>

rpc:call(<RQ_Nodename>, erlang, statistics, [garbage_collection]).
-Hemant


On Wed, Sep 3, 2014 at 4:54 AM, David Medberry <openstack at medberry.net>
wrote:

>
> On Tue, Sep 2, 2014 at 2:25 PM, Andy Hill <hillad at gmail.com> wrote:
>
>>
>> http://virtualandy.wordpress.com/2014/09/02/operating-openstack-monitoring-rabbitmq/
>
>
>
> Nice writeup Andy, thanks for sharing!
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20140909/c20f97e2/attachment.html>