We had some issues related to this too, we ended up changing our
collect_statistics_interval to 30 seconds as opposed to the default which is 5
I think.
We also upgraded to 3.6.2 and that version is very buggy and wouldn’t recommend
anyone to use it. It has a memory leak and some other nasty
Hi Joshua,
Does this happen with `rates_mode` set to `none` and tuned
`collect_statistics_interval`? Like in
https://bugs.launchpad.net/fuel/+bug/1510835
High connection/channel churn during upgrade can cause such issues.
BTW, soon-to-be-released rabbitmq 3.6.3 contains several improvements
Hi ops and dev-folks,
We over at godaddy (running rabbitmq with openstack) have been hitting a
issue that has been causing the `rabbit_mgmt_db` consuming nearly all
the processes memory (after a given amount of time),
We've been thinking that this bug (or bugs?) may have existed for a
while
