I mostly failed to explain the impact of the above Erlang bugs. Due to ERl-430 and ERL-448 above, nodes that had any TCP connections open (possibly from HTTP requests) could fail to stop (shut down), accept new TCP connections (including from HTTP clients, RabbitMQ CLI tools) and respond on already open TCP connections.
All of those behaviors are particularly problematic during upgrades. In fact, it was discovered as part of an upgrade of the RabbitMQ BOSH release [1]. 1. https://github.com/pivotal-cf/cf-rabbitmq-release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783203 Title: Upgrade to RabbitMQ 3.6.10 causes beam lockup in clustered deployment To manage notifications about this bug go to: https://bugs.launchpad.net/charm-rabbitmq-server/+bug/1783203/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
