Note there was a bug in rabbitmq (3.1.0) that prevented the stop from working correctly:
26027 ensure autoheal does not hang winner node if 'rabbitmqctl stop_app' issued on other node during healing (since 3.1.0)
This is the reason for the lock-up on stop. Fixing this revealed the clustering restart scripting is not robust and needs some rework.
Note there was a bug in rabbitmq (3.1.0) that prevented the stop from working correctly:
26027 ensure autoheal does not hang winner node if 'rabbitmqctl stop_app'
issued on other node during healing (since 3.1.0)
This is the reason for the lock-up on stop. Fixing this revealed the clustering restart scripting is not robust and needs some rework.