[rabbitmq-discuss] Stats node getting slow
simon at rabbitmq.com
Mon Nov 11 09:52:38 GMT 2013
On 11/11/2013 9:45AM, Simon MacMullen wrote:
> Hmm, the stats DB was more or less rewritten between 3.0.x and 3.1.0 (to
> keep stats histories). If there's a memory leak in there I'd very much
> like to get to the bottom of it.
Of course the other possibility is that the stats DB is simply
overwhelmed with work and unable to keep up. It's supposed to start
dropping incoming stats messages in this situation, but maybe it isn't.
To determine if this is the case, look at:
rabbitmqctl eval 'process_info(global:whereis_name(rabbit_mgmt_db),
- and if the number that comes back looks like it would account for most
of the memory used, then that is likely to be the problem. In that case
you can slow down stats event emission by changing
collect_statistics_interval (see http://www.rabbitmq.com/configure.html)
and / or disable fine-grained stats as I mentioned in the previous message.
More information about the rabbitmq-discuss