[rabbitmq-discuss] Possible memory leak in the management plugin

Pavel pmaisenovich at blizzard.com
Fri Apr 11 04:12:41 BST 2014

I'm attaching three tests data. 

In Test 2 and 3 there was 1000 channels x 999 exchanges with only difference
in publish rate. Both tests led to Rabbit running OOM (high watermark) and
throttling publishers. One new thing I noted after plotting the
mgmt_stats_db used memory is that it spikes rapidly shortly before
throttling triggered. This is not related to continuous aggregated_stats
growth (or it doesn't seem so), but also very concerning.

In Test 4 (which is still running) I've reduced number of channels and
exchanges by half (500 and 499) to prove the theory of aggregated_stats
growth. As you can see from the plot, the number of items in
aggregated_stats table have not changed for about an hour, yet the size of
the table continues to grow. It's worth noting, that while Rabbit didn't
reach high watermark (current usage is [{total,2884223408},
{mgmt_db,1764414344}]) in this test (yet), the management plugin UI is
completely unresponsive. The test continues to publish at a steady 500/s
rate and I'll leave for the night to see how far it will push the RAM.




View this message in context: http://rabbitmq.1065348.n5.nabble.com/Possible-memory-leak-in-the-management-plugin-tp27414p34791.html
Sent from the RabbitMQ mailing list archive at Nabble.com.

More information about the rabbitmq-discuss mailing list