diff options
author | Matthias Radestock <matthias@rabbitmq.com> | 2014-04-14 12:36:06 +0100 |
---|---|---|
committer | Matthias Radestock <matthias@rabbitmq.com> | 2014-04-14 12:36:06 +0100 |
commit | 5784cd7ed58251decaa003a9fb0540adc23b749d (patch) | |
tree | b87c12722ea61045b74b92aa60260319f1083d9d | |
parent | 3a3b67e62ad22ddb7d0eedb2a93d1bcf247d26bf (diff) | |
download | rabbitmq-server-5784cd7ed58251decaa003a9fb0540adc23b749d.tar.gz |
eliminate comment duplication
-rw-r--r-- | src/rabbit_mirror_queue_slave.erl | 5 |
1 files changed, 1 insertions, 4 deletions
diff --git a/src/rabbit_mirror_queue_slave.erl b/src/rabbit_mirror_queue_slave.erl index c18eff13..ee9f7701 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. |