[SERVER-84171] findAndModify command may fail with NamespaceNotFound if the database is concurrently dropper Created: 14/Dec/23 Updated: 15/Dec/23 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Antonio Fuschetto | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | car-qw | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Story Points: | 1 | ||||||||
| Description |
Problem descriptionAs 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 solutionThe problem and solution are very similar to User impactsThe real risk that a user will experience the problem is very low. However, it could occur in continuous integration (as happened for |