[SERVER-82811] ShardsvrProcessInterface::dropCollection should accept NamespaceNotFound errors due to the database having been dropped Created: 06/Nov/23  Updated: 22/Nov/23  Resolved: 22/Nov/23

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

Type: Task 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-79693 Improve MongoProcessInterface methods... Closed
Assigned Teams:
Catalog and Routing
Backwards Compatibility: Fully Compatible
Sprint: CAR Team 2023-11-27
Participants:

 Description   

ShardsvrProcessInterface::dropCollection routes _shardsvrDropCollection to the db-primary shard for the collection to be dropped. If its database does not exist anymore, it will fail with NamespaceNotFound, even though the collection does no longer exist so it should be considered a success.



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

Author:

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

Message: SERVER-82811 ShardsvrProcessInterface::dropCollection should accept NamespaceNotFound errors due to the database having been dropped
Branch: master
https://github.com/mongodb/mongo/commit/3edeea220267ceab77bb68a880df575fae7c8281

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