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

Don't perform a ShardingLog under the kChunkLock

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 7.0.0, 8.0.0
    • Component/s: None
    • Catalog and Routing
    • CAR Team 2024-12-23
    • 1

      We've noticed that performing a ShardingLog like this one may take a large amount of time.

      A few ShardingLog's are executed under the kChunkLock, which adds unnecessary latency to those operations waiting for the lock.

      This task aims to release the kChunkLock before performing any ShardingLogs.

            Assignee:
            Unassigned Unassigned
            Reporter:
            silvia.surroca@mongodb.com Silvia Surroca
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: