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

Tenant collection cloner should handle dropped and re-created collections on resume

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 5.0.0-rc2, 5.1.0-rc0
    • None
    • Fully Compatible
    • ALL
    • v5.0
    • Repl 2021-06-28
    • 43

    Description

      If a collection is dropped and re-created (under a different uuid that's compared larger than the old one) on the donor during recipient failovers, when the new recipient primary tries to resume the collection cloning stage, it is possible to hit this uassert with NamespaceExists if the old recipient primary already created the collection of the same namespace under the old uuid.

      Attachments

        Issue Links

          Activity

            People

              lingzhi.deng@mongodb.com Lingzhi Deng
              lingzhi.deng@mongodb.com Lingzhi Deng
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: