canonical-ubuntu-qa team mailing list archive

[Paride Legovini <mp+453319@xxxxxxxxxxxxxxxxxx>]

I am not a fan of the restart approach. Maybe we should try using a newer rabbitmq. This is from the the upstream git history:

$ git log --oneline v3.8.2.. | grep -i 'mem.*leak'
6806a9a45e Fixes a memory leak in AMQP 1.0 plugin (#7015)
db2e858cf1 Fix memory leaks
bc1a912af8 Use `raw` option for `file:read_file_info/2` to work around win32 mem leak erlang/otp#5527
6a01d80ebe Fix win32 memory leak by using `raw` file operations. Not ideal but this skips all file servers.
2ec8596597 Merge pull request #3906 from rabbitmq/lukebakken/fix-mem-leak
20977f68fd Use `raw` option for `file:read_file_info/2` to work around win32 mem leak erlang/otp#5527
458306dc8b Fix win32 memory leak by using `raw` file operations. Not ideal but this skips all file servers.
7ffb154787 Fix memory leak when using mandatory flag in CQs
5779059bd5 QQ: fix memory leak when cancelling consumer
5b9311b846 Fixes the "zombie" direct connections, when using Federated Exchanges and forcibly closing the upstream connections. This happens deterministically 100% of the time. The fact that direct connections do not close, causes a process and memory leak on RabbitMQ.

-- 
https://code.launchpad.net/~andersson123/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/453319
Your team Canonical's Ubuntu QA is requested to review the proposed merge of ~andersson123/autopkgtest-cloud:add_rabbitmq_cleanup_to_rabbitmq_unit into autopkgtest-cloud:master.