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

Optimize collection level path taking collection lock instead of db lock at checkMetadataConsistencyParticipant

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 7.1.0-rc0
    • None
    • None
    • Sharding EMEA
    • Fully Compatible
    • Sharding EMEA 2023-05-01, Sharding EMEA 2023-05-15, Sharding EMEA 2023-05-29

    Description

      In case of collection level, there is no need to lock the database, we could simply need to lock the collection.

      The goal of this ticket is to optimize the path for checkMetadataConsistencyParticipant when the cmd is run at collection level.

      Attachments

        Activity

          People

            pol.pinol@mongodb.com Pol Pinol
            pol.pinol@mongodb.com Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: