[rabbitmq-discuss] Management API hangs after upgrade from 3.1.5 to 3.2.3

Greg Poirier greg.poirier at opower.com
Sun Feb 16 18:26:59 GMT 2014

This weekend, I upgraded one of our RabbitMQ clusters from 3.1.5 to 3.2.3.

After the upgrade, the management API has become somewhat unstable.
Somewhere around 20% of the time, requests to the API stall. For example, a
simple curl of the aliveness test endopint stalls after the GET request is
sent (as seen via tcpdump). The management plugin simply never responds.

This is causing our basic aliveness and partition checks to fail on this
cluster pretty regularly.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140216/0f403ed9/attachment.html>

More information about the rabbitmq-discuss mailing list