mon/MonClient: un-backoff on tick when we have a authenticated session

This means that if we do some backoff, then authenticate, and are healthy
for an extended period of time, a subsequent failure won't leave us
starting our hunting sequence with a large backoff.

Fixes: http://tracker.ceph.com/issues/20371
Signed-off-by: Sage Weil <sage@redhat.com>

diff --git a/src/mon/MonClient.cc b/src/mon/MonClient.cc
index 96975b31c528dc87bdc65c497f7e2aecbf6163ef..a0cd1e923c8ee2bbc023a7b08e5ee8ccd15149f9 100644 (file)
--- a/src/mon/MonClient.cc
+++ b/src/mon/MonClient.cc
@@ -769,6 +769,8 @@ void MonClient::tick()
 
       send_log();
     }
+
+    _un_backoff();
   }
 
   schedule_tick();