-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
ALL
-
CAR Team 2024-03-18
-
1
Problem description
As a part of the logic of the findAndModify command, the router check and possibly implicitly create the database then get the routing information for the involved collection.
If the database is dropped in the meantime (before the two events above), the command fails with NamespaceNotFound error.
Potential solution
The problem and solution are very similar to SERVER-83146.
User impacts
The real risk that a user will experience the problem is very low. However, it could occur in continuous integration (as happened for SERVER-83146).
- is fixed by
-
SERVER-85843 A write operation may fail with NamespaceNotFound if the database has been concurrently dropped (sharding-only)
- Closed
- is related to
-
SERVER-83146 Bulk write operation might fail with NamespaceNotFound
- Closed