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

Legacy renameCollection may proceed renaming a sharded collection

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 5.0.0-rc1
    • 5.0.0-rc3, 5.1.0-rc0
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • v5.0
    • Sharding EMEA 2021-06-28
    • 120

    Description

      The legacy-path renameCollection must fail if either the source or the destination collections are sharded.
      It does so by checking if the filtering metadata has the collection as sharded or not.

      There is a situation where after a shardCollection operations has completed writing the config.chunks and config.collections documents, but then steps down before refreshing the filtering metadata, where the new primary may be left with filtering metadata as unsharded. Under that scenario, a legacy-path rename may succeed in renaming a sharded collection.

      Attachments

        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:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: