Safely handle (and log) anonymous info messages, most likely

from the gm process' neighbours

1 files changed, 8 insertions, 1 deletions

diff --git a/src/gm.erl b/src/gm.erl
index 176e14537f..822d50252b 100644
--- a/src/gm.erl
+++ b/src/gm.erl
@@ -757,7 +757,14 @@ handle_info({'DOWN', MRef, process, _Pid, Reason},
     catch
         lost_membership ->
             {stop, normal, State}
-    end.
+    end;
+handle_info(Msg, State = #state { self = Self }) ->
+    %% TODO: For #gm_group{} related info messages, it could be worthwhile to
+    %% change_view/2, as this might reflect an alteration in the gm group, meaning
+    %% we now need to update our state. see rabbitmq-server#914.
+    rabbit_log:info("GM member ~p received unexpected message ~p~n"
+                    "When Server state == ~p", [Self, Msg, State]),
+    noreply(State).
 
 terminate(Reason, #state { module = Module, callback_args = Args }) ->
     Module:handle_terminate(Args, Reason).