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

MigrationDestinationManager assigns incorrect timestamps while building multiple indexes

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.0.7, 4.1.7
    • Affects Version/s: 4.0.5, 4.1.6
    • Component/s: Storage
    • None
    • Fully Compatible
    • ALL
    • v4.0
    • Storage NYC 2018-12-31

      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.

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

              Created:
              Updated:
              Resolved: