[rabbitmq-discuss] RabbmitMQ consuming CPU and Memory

Mon May 14 19:48:57 BST 2012

> There have been numerous stability improvements since 2.7.1, so I 
> suggest you upgrade to the latest rabbit version (2.8.2). Also, R13B03 
> is quite ancient, so you should really upgrade that too - R15B01 is 
> the latest.
>
> If you still see the same behaviour then try to set up some alarms 
> that catch the problem in the early stages and grab the output of 
> 'rabbitmqctl report'.
>
We are working on upgrading our rabbitmq and erlang. In the mean time, 
here is the output of 'rabbitmqctl report' on a MacPro right after 
rabbitmq went crazy before we had to kill it. Is there something unusual 
in these numbers?

[{pid,70356},
  {running_applications,[{rabbit,"RabbitMQ","2.7.1"},
                         {mnesia,"MNESIA  CXC 138 12","4.6"},
                         {os_mon,"CPO  CXC 138 46","2.2.8"},
                         {sasl,"SASL  CXC 138 11","2.2"},
                         {stdlib,"ERTS  CXC 138 10","1.18"},
                         {kernel,"ERTS  CXC 138 10","2.15"}]},
  {os,{unix,darwin}},
  {erlang_version,"Erlang R15B (erts-5.9) [source] [64-bit] [smp:16:16] [async-threads:30] [hipe] [kernel-poll:true]\n"},
  {memory,[{total,90264888},
           {processes,65595873},
           {processes_used,65591050},
           {system,24669015},
           {atom,504409},
           {atom_used,475985},
           {binary,6765008},
           {code,11916223},
           {ets,1291168}]},
  {vm_memory_high_watermark,0.3999999999026046},
  {vm_memory_limit,3285576908}]

Cluster status of node rabbit at yoshi ...
[{nodes,[{disc,[rabbit at yoshi]}]},{running_nodes,[rabbit at yoshi]}]

Application environment of node rabbit at yoshi ...
[{auth_backends,[rabbit_auth_backend_internal]},
  {auth_mechanisms,['PLAIN','AMQPLAIN']},
  {backing_queue_module,rabbit_variable_queue},
  {cluster_nodes,[]},
  {collect_statistics,none},
  {collect_statistics_interval,5000},
  {default_permissions,[<<".*">>,<<".*">>,<<".*">>]},
  {default_user,<<"guest">>},
  {default_user_tags,[administrator]},
  {default_vhost,<<"/">>},
  {delegate_count,16},
  {error_logger,{file,"/usr/local/var/log/rabbitmq/rabbit at yoshi.log"}},
  {frame_max,131072},
  {hipe_compile,false},
  {included_applications,[]},
  {msg_store_file_size_limit,16777216},
  {msg_store_index_module,rabbit_msg_store_ets_index},
  {queue_index_max_journal_entries,262144},
  {sasl_error_logger,{file,"/usr/local/var/log/rabbitmq/rabbit at yoshi-sasl.log"}},
  {server_properties,[]},
  {ssl_listeners,[]},
  {ssl_options,[]},
  {tcp_listen_options,[binary,
                       {packet,raw},
                       {reuseaddr,true},
                       {backlog,128},
                       {nodelay,true},
                       {exit_on_close,false}]},
  {tcp_listeners,[5672]},
  {trace_vhosts,[]},
  {vm_memory_high_watermark,0.4}]

Connections:

Channels:

Queues on /:

Exchanges on /:
name	type	durable	auto_delete	internal	arguments
amq.direct	direct	true	false	false	[]
amq.topic	topic	true	false	false	[]
amq.rabbitmq.trace	topic	true	false	false	[]
amq.rabbitmq.log	topic	true	false	false	[]
amq.fanout	fanout	true	false	false	[]
amq.headers	headers	true	false	false	[]
	direct	true	false	false	[]
amq.match	headers	true	false	false	[]

Bindings on /:

Consumers on /:

Permissions on /:
user	configure	write	read
guest	.*	.*	.*

End of server status report
...done.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120514/90e5ba9e/attachment.htm>