[rabbitmq-discuss] Possible memory leak in the management plugin
simon at rabbitmq.com
Fri Apr 11 14:51:21 BST 2014
On 11/04/2014 00:17, Pavel wrote:
> aggregated_stats table was
> growing steadily for almost 4 hours straight until it reached 2.5Gb
One thing occurs to me: the ETS GC part of the management DB decides on
how many rows to GC per iteration in advance, at the start of each run
through the table.
So if you started with 10,000 rows in the table, it would decide to read
100 rows at a time. If the table then increased to 1,000,000 rows it
would still only manage 100 at a time until it had traversed the table
completely - taking most of a day to do so.
And your test rather resembles this case.
So the GC code probably needs to be smarter about how it does this.
More information about the rabbitmq-discuss