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)

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.0.0-rc0, 5.0.26, 6.0.15, 7.0.7, 7.3.2
    • Affects Version/s: 4.4.0, 5.0.0, 6.0.0, 7.0.0, 7.3.0-rc1
    • Component/s: None
    • Labels:
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • v7.3, v7.0, v6.0, v5.0
    • Hide

      See the attached patch file.

      See the attached patch file.
    • CAR Team 2024-02-19, CAR Team 2024-03-04, CAR Team 2024-03-18
    • 7
    • 1

      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.

            adam.farkas@mongodb.com Wolfee Farkas
            antonio.fuschetto@mongodb.com Antonio Fuschetto
            0 Vote for this issue
            6 Start watching this issue