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

Two phase index build completion should use timestamp from commitIndexBuild oplog entry

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.1
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • Execution Team 2019-10-07, Execution Team 2019-10-21

      When two phase index builds are enabled, timestamp_index_builds.js currently fails in the third phase of the test where the node is restarted as a standalone node. The underlying issue seems to be that the completion of a two phase index build, represented in the oplog by the commitIndexBuild oplog entry, is not timestamped correctly. Currently, we obtain a ghost timestamp for the purposes of writing to the mdb catalog on a successful index build. Now that we have the commitIndexBuild oplog entry, we should be able use a timestamp that is present in the oplog.

            Assignee:
            benety.goh@mongodb.com Benety Goh
            Reporter:
            louis.williams@mongodb.com Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: