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

A write operation may fail with NamespaceNotFound if the database has been concurrently dropped (sharding-only)

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • 4.4.0, 5.0.0, 6.0.0, 7.0.0, 7.3.0-rc1
    • None
    • None
    • Catalog and Routing
    • ALL
    • Hide

      See the attached patch file.

      Show
      See the attached patch file.
    • 7
    • 1

    Description

      When a write is targeted, the router ensures the target database is created by using the cluster DDL API. However, if the database is subsequently dropped before the collection refresh in the insert path, the operation fails with NamespaceNotFound error.

      A variant of this problem was already fixed in the context of SERVER-83146. However, there are multiple scenarios where the problem can still occur. The management of the time-series collections required multiple paths that must be reviewed in the context of this fix.

      The probability of the problem occurring in a real-world scenario is negligible. The cost of the fix is a couple of days at most.

      Attachments

        Activity

          People

            backlog-server-catalog-and-routing Backlog - Catalog and Routing
            antonio.fuschetto@mongodb.com Antonio Fuschetto
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated: