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

OplogStartHack should use the requested yield policy

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.2.0-rc2, 4.3.1
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.2
    • Sprint:
      Query 2019-06-17
    • Linked BF Score:
      17

      Description

      SERVER-41222 attempted to give the TransactionHistoryIterator the ability to specify an "interrupt only" policy for its PlanExecutor, but when the executor is created with an OplogStartHack (which should be always in the case of the TransactionHistoryIterator), it still uses the regular YIELD_AUTO policy.

      The solution is simply to propagate the policy value from _getExecutorFind() all the way into the getOplogStartHack call.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: