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

Make copyDb transfer over UUIDs when it is called in metadataOnly mode

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 3.7.4
    • None
    • None
    • None
    • Fully Compatible
    • Sharding 2018-03-12, Sharding 2018-03-26

    Description

      SERVER-32643 adds a metadataOnly mode to Cloner::copyDb, to be used when clone is called by configsvrMovePrimary.

      Currently, copyDb uses Cloner::filterOptionsForClone to select out the info to copy over to the new instance of the DB. At that point it drops the UUIDs, but when we are using clone for movePrimary, we want to keep the UUIDs consistent since it is all one collection.

      We should change filterOptionsForClone so that when metadataOnly=true, we either
      a) verify the UUIDs match if the collection already exists on the new primary, or
      b) use the collection's UUID from the old primary when we create it for the first time on the new primary.

      Attachments

        Activity

          People

            janna.golden@mongodb.com Janna Golden
            kaitlin.mahar@mongodb.com Kaitlin Mahar
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: