DatabaseCloner fails to parse CollectionOptions if listCollections returns metadata with UUIDs

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.5.8
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2017-05-29
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      If we attempt to start up a replica set with more than one node and enable collection UUIDs (--setParameter=enableCollectionUUIDs=true), the initial sync will fail because of the new UUIDs included in the collection metadata returned by listCollections. This is because DatabaseCloner is using a mode of CollectionOptions::parse() that is more suited to validating CollectionOptions provided by the user at collection creation time, not an existing CollectionOptions with a generated UUID.

              Assignee:
              Benety Goh
              Reporter:
              Benety Goh
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: