crimson/osd: write log when sending "osd_failure" msg

Signed-off-by: Kefu Chai <kchai@redhat.com>

diff --git a/src/crimson/osd/heartbeat.cc b/src/crimson/osd/heartbeat.cc
index 6103bdf53cedbe303da4fd173a5841a90f10472a..bd7f906f322e1a38247bc9f5a7af96f43f8e678d 100644 (file)
--- a/src/crimson/osd/heartbeat.cc
+++ b/src/crimson/osd/heartbeat.cc
@@ -649,6 +649,7 @@ bool Heartbeat::FailingPeers::add_pending(
   failure_pending.emplace(peer, failure_info_t{failed_since,
                                                osdmap->get_addrs(peer)});
   futures.push_back(heartbeat.monc.send_message(failure_report));
+  logger().info("{}: osd.{} failed for {}", __func__, peer, failed_for);
   return true;
 }
 
@@ -674,5 +675,6 @@ Heartbeat::FailingPeers::send_still_alive(
     0,
     heartbeat.service.get_osdmap_service().get_map()->get_epoch(),
     MOSDFailure::FLAG_ALIVE);
+  logger().info("{}: osd.{}", __func__, osd);
   return heartbeat.monc.send_message(still_alive);
 }