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

Avoid ShardingRoutingInfoFormatStability serializing DDL operations on the same shard

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Duplicate
    • None
    • None
    • Sharding

    Description

      Since SERVER-53092 we are using the "
      ShardingRoutingInfoFormatStability" DistLock to ensure that DDL operations serialize with the patch up of metadata in the configsvr during FCV upgrade. This is to ensure DDL operations see a stable metadata format.
      Currently, the DistLock serializes between shards and the configsvr or between threads on the same shard
      For ShardingRoutingInfoFormatStability, we only wish to serialize between the configsvr and that shards, but not serialize DDL operations on the same shard.
      For this, we could expose a "lockOnlyRemote" variant of the DistlockManager::lock that only serializes with the configsvr, and use it for the ShardingRoutingInfoFormatStability.

      Attachments

        Issue Links

          Activity

            People

              backlog-server-sharding-emea Backlog - Sharding EMEA
              jordi.serra-torrens@mongodb.com Jordi Serra Torrens
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: