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

"Ghost" timestamp must set transaction to unordered

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.2.6, 4.4.0-rc0, 4.7.0
    • Component/s: Indexing
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.4, v4.2
    • Sprint:
      Execution Team 2020-01-13, Execution Team 2020-01-27, Execution Team 2020-02-10, Execution Team 2020-02-24, Execution Team 2020-03-09, Execution Team 2020-03-23, Execution Team 2020-04-06
    • Linked BF Score:
      23

      Description

      When we cancel an index build, we do some writes at a "ghost" timestamp (one which may or may not correspond to an oplog entry). The existence of this "ghost" timestamp may hold oplog visibility back, so when we complete the write we need to trigger oplog visibility to be refreshed. That only happens if the transaction is set to unordered (setOrderedCommit(false)).

        Attachments

          Activity

            People

            Assignee:
            daniel.gottlieb Daniel Gottlieb
            Reporter:
            matthew.russotto Matthew Russotto
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: