Invalidate filtering info on participants at the end of renameCollection

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.0.0-rc1, 5.1.0-rc0
    • Affects Version/s: 5.0.0-rc0
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • v5.0
    • Sharding EMEA 2021-06-14
    • 46
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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'.

            Assignee:
            Jordi Serra Torrens
            Reporter:
            Jordi Serra Torrens
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: