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

Track time spent waiting for refresh on the router

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 6.1.0-rc0
    • None
    • None
    • Fully Compatible
    • Sharding EMEA 2022-06-27, Sharding EMEA 2022-07-11, Sharding EMEA 2022-07-25, Sharding EMEA 2022-08-08

    Description

      As a second part of tracking the time CRUD operations spend waiting for metadata refresh, we should add to the slow query log the time taken waiting for routing information. This could potentially reuse the timing in totalRefreshWaitTimeMicros.

      Attachments

        Issue Links

          is related to

          Task - A task that needs to be done. SERVER-67252 Track time spent waiting for refresh on the shards

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-56304 Log time CRUD operations spend waiting for metadata refresh

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              allison.easton@mongodb.com Allison Easton
              allison.easton@mongodb.com Allison Easton
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: