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

Timestamp drained writes from the index build side table to the index

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.1.8
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • Storage NYC 2019-01-28, Storage NYC 2019-02-11
    • 0

      In order for rollback/restart to work properly with resuming simultaneous index builds work in the draining phase, secondaries must start picking timestamps at which to do certain writes so that recover to a stable timestamp moves all the information backwards in concert. Note these timestamps will not be associated with a unique oplog entry.

      The writes needing timestamps:
      1) Index catalog entry updates, for example to track index build phases to know if the build is recoverable or must be restarted from scratch this will be done in SERVER-37645
      2) Deletes from thee side table when draining & subsequent writes to the index, which occur in the same transaction with the same timestamp.

            Assignee:
            louis.williams@mongodb.com Louis Williams
            Reporter:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: