Cloner::copyDb should handle the scenario where a collection already exists before calling IndexBuildsCoordinator::createIndexesOnEmptyCollection and hitting an invariant

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Sharding NYC
    • ALL
    • 9
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      I don't see any obvious checks done in the Cloner code before calling createIndexesOnEmptyCollection, which may hit an invariant if the collection exists. Cloner should error and log more information in such scenarios.

            Assignee:
            Nandini Bhartiya
            Reporter:
            Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: