resumable index build should use majority read cursor for collection scan

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.7.0
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • Execution Team 2020-06-15, Execution Team 2020-06-29, Execution Team 2020-07-13
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      For resumable index builds, in order to ensure that we do not need to roll back any of the keys inserted into the sorter, the collection scan should start at a timestamp that has been majority committed. We will also need to ensure that the side writes table doesn't miss any writes. When we initially begin the collection scan, we must first install the side writes interceptor and then wait for the last oplog entry (the last entry that was not captured by the interceptor) to become majority committed, before establishing the snapshot to read the collection.

            Assignee:
            Samyukta Lanka
            Reporter:
            Benety Goh
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: