Using index builder on primaries does not timestamp index build completion

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.0.0-rc0
    • Affects Version/s: None
    • Component/s: Replication, Storage
    • None
    • Fully Compatible
    • ALL
    • Storage NYC 2018-05-21
    • 76
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Daniel Gottlieb (Inactive)
            Reporter:
            Daniel Gottlieb (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: