Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-61735

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

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.3.0
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Fully Compatible
    • Sharding EMEA 2022-01-10

      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.

            Assignee:
            jordi.serra-torrens@mongodb.com Jordi Serra Torrens
            Reporter:
            jordi.serra-torrens@mongodb.com Jordi Serra Torrens
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: