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

dropAggTempCollections should accept NamespaceNotFound errors due to the db having been dropped

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • CAR Team 2023-11-27

      dropAggTempCollections drops the temporary collections listed on 'config.agg_temp_collections', in a sharding-aware way (i.e. by routing _shardsvrDropCollection to the db-primary shard). However, if the database has been dropped, this routing will fail with NamespaceNotFound. In this case, the temp colleciton was already dropped, so the collection should be delisted from 'config.agg_temp_collections'.

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

              Created:
              Updated:
              Resolved: