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

applyOps should return NamespaceNotFound when applying a CRUD operation on a non-existent collection/database

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.4.10, 3.6.0-rc0
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Completed:
    • Linked BF Score:
      0

      Description

      Currently applyOps relies on lower level subsystems such as the catalog or query execution subsystem to handle CRUD operations that refer to non-existent collections or databases. Some CRUD operations, such as update/upserts, may implicitly create a collection as a result. We should uniformly reject any CRUD operations on non-existent namespaces in apply_ops.cpp (within the _applyOps() function).

        Attachments

          Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-31471 Certain applyOps and convertToCapped commands can cause secondaries to fassert

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-27246 Running applyOps with an op on a nonexistent database using mmapv1 will crash mongod

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: