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

Using index builder on primaries does not timestamp index build completion

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0.0-rc0
    • Component/s: Replication, Storage
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Storage NYC 2018-05-21
    • Linked BF Score:
      76

      Description

      Typically indexes on primaries are built via a user command. However there are a few instances where index builds can complete on a node that identifies as a primary, but managed by the IndexBuilder class. Specifically:

      • Primary catchup
      • Primary drain
      • Started on a secondary, but complete after a step-up

      Primaries (and other states) do not timestamp index completion. For primaries, it was expected that committing the index build writes an oplog entry, timestamping the transaction.

      Instead, consider having callers of MultiIndexBlock manage timestamping the write.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              daniel.gottlieb Daniel Gottlieb
              Reporter:
              daniel.gottlieb Daniel Gottlieb
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: