SERVER-61735 Add a new timing log step in MigrationDestinationManager to track the time waiting for critical section release

1 files changed, 5 insertions, 3 deletions

diff --git a/src/mongo/db/s/migration_destination_manager.cpp b/src/mongo/db/s/migration_destination_manager.cpp
index 8cf648fae60..b4e4ef44918 100644
--- a/src/mongo/db/s/migration_destination_manager.cpp
+++ b/src/mongo/db/s/migration_destination_manager.cpp
@@ -1092,7 +1092,7 @@ void MigrationDestinationManager::_migrateDriver(OperationContext* outerOpCtx,
 
     if (!skipToCritSecTaken) {
         timing.emplace(
-            outerOpCtx, "to", _nss.ns(), _min, _max, 7 /* steps */, &_errmsg, _toShard, _fromShard);
+            outerOpCtx, "to", _nss.ns(), _min, _max, 8 /* steps */, &_errmsg, _toShard, _fromShard);
 
         LOGV2(
             22000,
@@ -1554,6 +1554,9 @@ void MigrationDestinationManager::_migrateDriver(OperationContext* outerOpCtx,
             return;
         }
 
+        timing->done(7);
+        migrateThreadHangAtStep7.pauseWhileSet();
+
         if (_acquireCSOnRecipient) {
             const auto critSecReason = criticalSectionReason(*_sessionId);
 
@@ -1622,8 +1625,7 @@ void MigrationDestinationManager::_migrateDriver(OperationContext* outerOpCtx,
     _setState(DONE);
 
     if (timing) {
-        timing->done(7);
-        migrateThreadHangAtStep7.pauseWhileSet();
+        timing->done(8);
     }
 }