When clustered, on application:stop, make sure we call on_node_node(node()). This is necessary because application:stop does not constitute a node failure, thus other nodes won't notice. Tested by creating a 2-node cluster, creating durable and non durable queues and checking that they're removed from mnesia tables as appropriate on application:stop on one of the nodes. Of course, even with the application stopped on one node, rabbitmqctl status still reports both nodes in the list of running_nodes. All tests pass.

1 files changed, 1 insertions, 1 deletions

diff --git a/src/rabbit.erl b/src/rabbit.erl
index c66a44a77e..29407e4e78 100644
--- a/src/rabbit.erl
+++ b/src/rabbit.erl
@@ -211,7 +211,7 @@ stop(_State) ->
     terminated_ok = error_logger:delete_report_handler(rabbit_error_logger),
     ok = rabbit_alarm:stop(),
     ok = case rabbit_mnesia:is_clustered() of
-             true  -> ok;
+             true  -> rabbit_amqqueue:on_node_down(node());
              false -> rabbit_mnesia:empty_ram_only_tables()
          end,
     ok.