[SERVER-61735] Add a new timing log step in MigrationDestinationManager to track the time waiting for critical section release Created: 25/Nov/21  Updated: 29/Oct/23  Resolved: 07/Jan/22

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.3.0

Type: Task Priority: Major - P3
Reporter: Jordi Serra Torrens Assignee: Jordi Serra Torrens
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2022-01-10
Participants:

 Description   

Before SERVER-58991, the 'step 7' of the MigrationDestinationManager timing object used to account up until the session cloner had finished. After SERVER-58991, in addition to that, it now also accounts for the time the MigrationDestinationManager waits for the release of its critical section.

We should restore the former semantics of 'step 7'; and introduce a new 'step 8', which exists only when the new migration protocol is in use that is stepped after the critical section has been exited.



 Comments   
Comment by Githook User [ 07/Jan/22 ]

Author:

{'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}

Message: SERVER-61735 Add a new timing log step in MigrationDestinationManager to track the time waiting for critical section release
Branch: master
https://github.com/mongodb/mongo/commit/05cf9f1fd13bedf9ad9a421d6ee8ad98351b4a06

Generated at Thu Feb 08 05:53:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.