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

renameCollection should re-register the source collection's UUID when interrupted

    • Type: Icon: Bug Bug
    • Resolution: Gone away
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.0.0-rc1, 4.1.1
    • Component/s: Catalog
    • ALL
    • Storage NYC 2018-12-31, Storage NYC 2019-01-28
    • 115

      It is possible to interrupt a renameCollection from "source" to "target" such that the UUID of "source" is no longer mapped to "source", but nothing at all.

      This can cause an invariant when using collMod to access the collection by UUID.

      The UUIDCatalog::onRenameCollection observer correctly implements this behavior, but because UUIDCatalog::onCreateCollection is called before the onRenameCollection observer is called, this leaves the UUID catalog in an incorrect state.

            Assignee:
            xiangyu.yao@mongodb.com Xiangyu Yao (Inactive)
            Reporter:
            louis.williams@mongodb.com Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: