monitor: assert out early if we get our own sync_start back

Signed-off-by: Greg Farnum <greg@inktank.com>

1 files changed, 7 insertions, 0 deletions

diff --git a/src/mon/Monitor.cc b/src/mon/Monitor.cc
index 0b4a44f1649..739f9b9d182 100644
--- a/src/mon/Monitor.cc
+++ b/src/mon/Monitor.cc
@@ -764,6 +764,13 @@ void Monitor::handle_sync_start(MMonSync *m)
 {
   dout(10) << __func__ << " " << *m << dendl;
 
+  /**
+   * This looks a bit odd, but we've seen cases where sync start messages
+   * get bounced around and end up at the originator without anybody
+   * noticing!
+   */
+  assert(m->reply_to != messenger->get_myinst());
+
   /* If we are not the leader, then some monitor picked us as the point of
    * entry to the quorum during its synchronization process. Therefore, we
    * have an obligation of forwarding this message to leader, so the sender