Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-84171

findAndModify command may fail with NamespaceNotFound if the database is concurrently dropped

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 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).

            Assignee:
            adam.farkas@mongodb.com Wolfee Farkas
            Reporter:
            antonio.fuschetto@mongodb.com Antonio Fuschetto
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: