Classic mirror queue memory Rapid memory allocation quickly leads to pod oom

[tianliuliu]

Describe the bug

Classic mirror queue memory result in pod oom, all the pod crash sequentially

RabbitMQ 3.11.8. Erlang 25.0.4
cluster has 42 queues and message avg size 1kb， all queues be applied by mirror policy like below

No large volume of network traffic was detected.

Reproduction steps

1.No idea was reproduced.

Expected behavior

not be oomed, it can be autoheal

Additional context

No response

[ansd]

RabbitMQ 3.11 is out of support

[michaelklishin]

@tianliuliu not sure if you have noticed but even RabbitMQ 4.0.x is out of community support, and 4.1.x will follow as of Feb 1, 2026.

Classic mirrored queues have been deprecated since mid-2021, have explicit warnings in red in the docs and there's specialized tooling for those still migrating from them.

And in 4.x, classic mirrored queues do not exist at all. Yes, now really is the time to begin that migration.