This issue was discovered at the scale lab, when rabbit nodes were running under load.
The issue is that stop_server_process() ignores exit code of the "rabbitmqctl stop" command and verifies the old rc value left from the latest pidfile check, which is wrong and leads to broken "stop" actions logic.
This issue appears only when stop action exceeds the given 60 sec timeout. That is a usual case under load, hence is critical by its impact.
This issue was discovered at the scale lab, when rabbit nodes were running under load. process( ) ignores exit code of the "rabbitmqctl stop" command and verifies the old rc value left from the latest pidfile check, which is wrong and leads to broken "stop" actions logic.
The issue is that stop_server_
This issue appears only when stop action exceeds the given 60 sec timeout. That is a usual case under load, hence is critical by its impact.