[SERVER-82810] dropAggTempCollections should accept NamespaceNotFound errors due to the db having been dropped Created: 06/Nov/23  Updated: 21/Nov/23  Resolved: 21/Nov/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.3.0-rc0

Type: Bug Priority: Major - P3
Reporter: Jordi Serra Torrens Assignee: Jordi Serra Torrens
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
is caused by SERVER-81444 Don't use temp:true collections for $... Closed
Assigned Teams:
Catalog and Routing
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: CAR Team 2023-11-27
Participants:

 Description   

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



 Comments   
Comment by Githook User [ 21/Nov/23 ]

Author:

{'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}

Message: SERVER-82810 dropAggTempCollections should accept NamespaceNotFound errors due to the db having been dropped
Branch: master
https://github.com/mongodb/mongo/commit/79e8901cff99f56033d49a9deba1a85d782f2239

Generated at Thu Feb 08 06:50:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.