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

applyOps collMod handling should only allow nonexistent UUIDs for UUID upgrade collMods

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.5.12
    • Component/s: Replication, Storage
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Storage 2017-08-21
    • Linked BF Score:
      0

      Description

      Currently, a collMod oplog entry with a nonexistent UUID will be applied to an existing collection if the collection name of the oplog entry matches an existing collection name. This is due to the handling of collMods that are used to upgrade from 3.4 to 3.6 and add UUIDs to collections. This special handling should only occur for collMods that are for upgrade, i.e., empty collMods.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: