OplogStartHack should use the requested yield policy

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.2.0-rc2, 4.3.1
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • v4.2
    • Query 2019-06-17
    • 17
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Justin Seyster
            Reporter:
            Justin Seyster
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: