A broker with no supported runtime left
A payments platform runs RabbitMQ 3.13 clusters with mirrored queues. Public 3.13 builds only run on Erlang/OTP 26, which left support in May 2026, and the move to 4.x means redesigning every mirrored queue.
Challenge
The runtime cannot be upgraded without the broker, and the broker cannot be upgraded until the queues move to quorum queues. Newer 3.13 fixes ship only in commercial releases, so the community build falls further behind every month.
Environment
Several RabbitMQ 3.13 clusters on Erlang/OTP 26, classic mirrored queues set by ha-mode policies, PCI DSS scope.
Approach
OSSeva ships patched RabbitMQ 3.13 and Erlang/OTP 26 builds through the client's repository, then runs the mirrored-to-quorum queue migration one vhost at a time.
What this delivers
A patched broker and runtime during the migration, and a planned route to RabbitMQ 4.x instead of a rushed one.