[rabbitmq-discuss] Rabbit Mq 3.0.2 memory leak

shridharan muthu shridharan.m at gmail.com
Mon Jan 13 17:47:53 GMT 2014

Hello again,

       I built a new recommended rabbit mq cluster with version 3.2.1
(Erlang R16B) to avoid the the memory leak issue that I mentioned in the
mail below. After building this cluster, I migrated 50% traffic on highest
volume queue (this queue constitutes to 70% of the total our traffic).

Cluster Version           v3.0.2                                  v3.2.1
Erlang                           R13B                                   R16B
# nodes                         2
# Connections             850                                      250
Erlang process            2900                                   1500
Publish/Delivery rate  230 / sec                            160 / sec
*Cpu Usage                   15%                                    25%*
*# Running process     2                                           3-4*

After the migration, I am noticing higher cpu usage and total number of
running processes on new cluster for less traffic than the original
cluster.  Also, when is there is an increase in traffic on both clusters,
cpu on new cluster increases significantly than increase in old cluster.
For instance, an increase in 0.4 MB network traffic over 2 mins caused an
increase in cpu of 2% in old cluster vs 6% increase in new cluster.

So I would like to understand why I am noticing increase in cpu and total
number of running processes before migration the whole traffic to new
cluster. Is this expected with new cluster?  I tried searching but couldn't
find any posts/blogs explaining this scenario.

Pls let me know if you need more info on cluster configs.


On Thu, Jan 2, 2014 at 6:44 AM, Emile Joubert <emile at rabbitmq.com> wrote:

> Hi,
> On 27/12/13 16:55, shridharan muthu wrote:
> > I know the quick answer is "upgrade" but is there a short term solution
> > to fix this before we upgrade?
> Please check whether you can reproduce the problem on the latest version
> of the broker. There have been numerous improvements to the broker since
> 3.0.2. If you can reproduce the problem then please supply the output of
> "rabbitmqctl report" while the memory usage is normal and again when it
> is abnormal.
> -Emile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140113/0f6d71a4/attachment.html>

More information about the rabbitmq-discuss mailing list