summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMatthias Radestock <matthias@rabbitmq.com>2014-04-14 12:36:06 +0100
committerMatthias Radestock <matthias@rabbitmq.com>2014-04-14 12:36:06 +0100
commitcc5c1404c97c0b9d22ce91bb50a1c33572a2794f (patch)
treeb87c12722ea61045b74b92aa60260319f1083d9d
parentd9f1c1b064708d94e4bbcaea885cfcadf51c9b11 (diff)
downloadrabbitmq-server-git-cc5c1404c97c0b9d22ce91bb50a1c33572a2794f.tar.gz
eliminate comment duplication
-rw-r--r--src/rabbit_mirror_queue_slave.erl5
1 files changed, 1 insertions, 4 deletions
diff --git a/src/rabbit_mirror_queue_slave.erl b/src/rabbit_mirror_queue_slave.erl
index c18eff13d0..ee9f77012b 100644
--- a/src/rabbit_mirror_queue_slave.erl
+++ b/src/rabbit_mirror_queue_slave.erl
@@ -405,10 +405,7 @@ handle_msg([_SPid], _From, {ensure_monitoring, _Pid}) ->
%% This is only of value to the master
ok;
handle_msg([_SPid], _From, process_death) ->
- %% Since GM is by nature lazy we need to make sure there is some
- %% traffic when a master dies, to make sure we get informed of the
- %% death. That's all process_death does, create some traffic. We
- %% must not take any notice of the master death here since it
+ %% We must not take any notice of the master death here since it
%% comes without ordering guarantees - there could still be
%% messages from the master we have yet to receive. When we get
%% members_changed, then there will be no more messages.