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

"Ghost" timestamp must set transaction to unordered

    • Fully Compatible
    • ALL
    • v4.4, v4.2
    • 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
    • 23

      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)).

            Assignee:
            daniel.gottlieb@mongodb.com Daniel Gottlieb (Inactive)
            Reporter:
            matthew.russotto@mongodb.com Matthew Russotto
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: