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

MigrationDestinationManager assigns incorrect timestamps while building multiple indexes

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 4.0.5, 4.1.6
    • 4.0.7, 4.1.7
    • Storage
    • None
    • Fully Compatible
    • ALL
    • v4.0
    • Storage NYC 2018-12-31

    Description

      When MigrationDestinationManager is cloning a collection with multiple indexes, the index builds are not assigned timestamps that are correct from a rollback/recovery perspective. A more detailed explanation of this issue is given in the resolved tickets SERVER-35780 and SERVER-35070.

      This issue was discovered while working on SERVER-37643.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-35070 multi index creates are given wrong timestamps

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-35780 `renameCollection` across databases incorrectly timestamps metadata for secondary index builds

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-37643 add createIndexes command logic to the index build interface

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              benety.goh@mongodb.com Benety Goh
              benety.goh@mongodb.com Benety Goh
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: