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

Invalidate filtering info on participants at the end of renameCollection

    XMLWordPrintable

Details

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

    Description

      Upon finishing a rename, there is currently no filtering metadata refresh (e.g like we do in createCollectionCoordinator). This can lead to a situation where, after renaming a sharded collection, the 'toNss' filtering metadata is incorrectly left as 'unsharded'.

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

            Dates

              Created:
              Updated:
              Resolved: