[rabbitmq-discuss] Rabbitmq 3.2.4 running out of memory

Wed Aug 27 01:53:52 BST 2014

Great one of the things I saw when the rabbitmq was running high memory ,
the plugin value is -ve

{erlang_version,
     "Erlang R14B04 (erts-5.8.5) [source] [64-bit] [smp:4:4] [rq:4]
[async-threads:30] [kernel-poll:true]\n"},
 {memory,
     [{total,9513029096},
      {connection_procs,190083816},
      {queue_procs,563064488},
      {plugins,-4964607832},
      {other_proc,5354348816},
      {mnesia,289348840},
      {mgmt_db,7437862072},
      {msg_index,16722336},
      {other_ets,50810936},
      {binary,253822816},
      {code,17776116},
      {atom,1622937},

here is the list of plugin enabled

[root at adsmv4218 ~]# rabbitmq-plugins list
[E] amqp_client                       3.2.4
[ ] cowboy                            0.5.0-rmq3.2.4-git4b93c2d
[ ] eldap                             3.2.4-gite309de4
[e] mochiweb                          2.7.0-rmq3.2.4-git680dba8
[ ] rabbitmq_amqp1_0                  3.2.4
[ ] rabbitmq_auth_backend_ldap        3.2.4
[ ] rabbitmq_auth_mechanism_ssl       3.2.4
[ ] rabbitmq_consistent_hash_exchange 3.2.4
[ ] rabbitmq_federation               3.2.4
[ ] rabbitmq_federation_management    3.2.4
[ ] rabbitmq_jsonrpc                  3.2.4
[ ] rabbitmq_jsonrpc_channel          3.2.4
[ ] rabbitmq_jsonrpc_channel_examples 3.2.4
[E] rabbitmq_management               3.2.4
[e] rabbitmq_management_agent         3.2.4
[ ] rabbitmq_management_visualiser    3.2.4
[ ] rabbitmq_mqtt                     3.2.4
[ ] rabbitmq_shovel                   3.2.4
[ ] rabbitmq_shovel_management        3.2.4
[E] rabbitmq_stomp                    3.2.4
[ ] rabbitmq_tracing                  3.2.4
[e] rabbitmq_web_dispatch             3.2.4
[ ] rabbitmq_web_stomp                3.2.4
[ ] rabbitmq_web_stomp_examples       3.2.4
[ ] rfc4627_jsonrpc                   3.2.4-git5e67120
[ ] sockjs                            0.3.4-rmq3.2.4-git3132eb9
[e] webmachine                        1.10.3-rmq3.2.4-gite9359c7

On Tue, Aug 26, 2014 at 5:46 PM, Michael Klishin <mklishin at pivotal.io>
wrote:

>  On 27 August 2014 at 04:44:04, srikanth tns (srikanthtns at gmail.com)
> wrote:
> > Is there any optimal value for global / basic policy ?
>
> If you're happy with the current RAM use levels for stats DB, I'd recommend
> leaving things as they are for a while.
>
> > Our needs
> > are to just monitor the number of connections and use that data
> > to load balance our connections.
>
> If you don't use message rates info, you probably don't need fine grained
> stats.
> Again, if things work for you as they are after the change, I'd leave it
> this way until the need to re-enable fine grained stats arises.
> --
> MK
>
> Staff Software Engineer, Pivotal/RabbitMQ
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140826/2c5c0ea8/attachment.html>