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

OplogStartHack should use the requested yield policy

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.2.0-rc2, 4.3.1
    • None
    • None
    • None
    • Fully Compatible
    • v4.2
    • Query 2019-06-17
    • 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

            justin.seyster@mongodb.com Justin Seyster
            justin.seyster@mongodb.com Justin Seyster
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: