Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Duplicate
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Sharding EMEA
Operating System:
ALL
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

Consider the following flow of execution:

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

duplicates

SERVER-60933 Make the sharded cluster's 'create' command behave the same as replica set

Closed

Assignee:: [DO NOT USE] Backlog - Sharding EMEA
Reporter:: Tommaso Tocci
Participants:: [DO NOT USE] Backlog - Sharding EMEA, Tommaso Tocci
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Jul 06 2022 10:21:08 PM UTC
Updated:: Dec 05 2022 11:58:34 PM UTC
Resolved:: Jul 07 2022 08:03:39 AM UTC