[SERVER-67828] Create collection on sharded cluster should not return NamespaceNotFound Created: 06/Jul/22  Updated: 05/Dec/22  Resolved: 07/Jul/22

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

Type: Bug Priority: Major - P3
Reporter: Tommaso Tocci Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-60933 Make the sharded cluster's 'create' c... Closed
Assigned Teams:
Sharding EMEA
Operating System: ALL
Participants:

 Description   

Consider the following flow of execution:

  1. mongos send a createColellection and receive a NamespaceExists error from the db primary shard
  2. the collection is dropped or renamed
  3. mongos calls checkCollectionOption and throws NamespaceNotFound since the collection doesn't exist anymore.

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