diff options
author | Matthew Sackman <matthew@lshift.net> | 2009-10-29 18:08:21 +0000 |
---|---|---|
committer | Matthew Sackman <matthew@lshift.net> | 2009-10-29 18:08:21 +0000 |
commit | 5a35aa20b59aad41a95fb1dbd720070584ddc488 (patch) | |
tree | d485dd7c63130691c5746bf523c05d3e88b74495 /generate_app | |
parent | 5cff5d8bf0cdd8475043dcb53a12ab2e52e66da3 (diff) | |
download | rabbitmq-server-5a35aa20b59aad41a95fb1dbd720070584ddc488.tar.gz |
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.bug21831
Diffstat (limited to 'generate_app')
0 files changed, 0 insertions, 0 deletions