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

The UUIDCatalog onCreateCollection observer should atomically unregister and re-register catalog entries

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.0.1, 4.1.1
    • Catalog
    • Fully Compatible
    • ALL
    • v4.0
    • Storage NYC 2018-07-02
    • 38

    Description

      DatabaseImpl::renameCollection uses the onCreateCollection UUID catalog observer, which does not atomically unregister and re-register the UUID of the collection being renamed.

      There is a race condition reading while the UUID is not registered to any collection. The recent addition of replaceUUIDCatalogEntry, which atomically swaps the UUIDs, should be used instead.

      The other problem of rename using the createCollection UUID catalog observer is tracked by SERVER-35319

      Attachments

        Issue Links

          Activity

            People

              ben.judd Ben Judd
              louis.williams@mongodb.com Louis Williams
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: