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

Ensure shard is primary shard for db on DDL operation legacy paths

    XMLWordPrintable

Details

    • Fully Compatible
    • ALL
    • v5.0
    • Sharding EMEA 2021-05-17, Sharding EMEA 2021-05-31

    Description

      Similarly to what we do in the new DDL coordinators, or even the legacy shard collection, we should ensure that the current shard is the primary shard for the DB. This is now necessary on the legacy DDL paths because they run on the shard. Otherwise, a request from a stale mongos could potentially execute on a non-primary shard.
      This needs to be addressed for the legacy dropCollection and dropDatabase

      Attachments

        Issue Links

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: