Closed jde closed 8 years ago
premature close on this. Memory issue persisted over the weekend. I'm having very good luck clearing the management console memory:
rabbitmqctl eval 'supervisor2:terminate_child(rabbit_mgmt_sup_sup, rabbit_mgmt_sup), rabbit_mgmt_sup_sup:start_child().'
Most if not all of the memory appears to be devoted to stats collection in rmq. Will wait a few days to confirm.
The terminate_child(...)
approach above resolved the issue. No need to update Go code.
We are seeing an ever increasing usage of memory coming from rabbitmq leading to server crashes.