From 5c64306487025e4acb3f1bd4059fc1e2441a7aa3 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Rados=C5=82aw=20Zarzy=C5=84ski?= Date: Wed, 13 Apr 2022 17:08:33 +0200 Subject: [PATCH] crimson/osd: CompoundPeeringRequest tracks its start and completion too MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit Signed-off-by: Radosław Zarzyński --- src/crimson/osd/osd_operations/compound_peering_request.cc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/crimson/osd/osd_operations/compound_peering_request.cc b/src/crimson/osd/osd_operations/compound_peering_request.cc index 286a8c0bb021d..86da1a47006a7 100644 --- a/src/crimson/osd/osd_operations/compound_peering_request.cc +++ b/src/crimson/osd/osd_operations/compound_peering_request.cc @@ -125,6 +125,7 @@ void CompoundPeeringRequest::dump_detail(Formatter *f) const seastar::future<> CompoundPeeringRequest::start() { logger().info("{}: starting", *this); + track_event(); auto state = seastar::make_lw_shared(); auto blocker = std::make_unique( [&] { @@ -146,6 +147,7 @@ seastar::future<> CompoundPeeringRequest::start() logger().info("{}: sub events complete", *this); return osd.get_shard_services().dispatch_context_messages(std::move(ctx)); }).then([this, ref=std::move(ref)] { + track_event(); logger().info("{}: complete", *this); }); }); -- 2.39.5