[SERVER-41589] OplogStartHack should use the requested yield policy Created: 07/Jun/19  Updated: 29/Oct/23  Resolved: 11/Jun/19

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.2.0-rc2, 4.3.1

Type: Improvement Priority: Major - P3
Reporter: Justin Seyster Assignee: Justin Seyster
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.2
Sprint: Query 2019-06-17
Participants:
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.



 Comments   
Comment by Githook User [ 21/Jun/19 ]

Author:

{'name': 'Justin Seyster', 'email': 'justin.seyster@mongodb.com', 'username': 'jseyster'}

Message: SERVER-41589 OplogStartHack should use the requested yield policy.

(cherry picked from commit 86b07826cede4cfd33e1a47f10a111b1d96e9758)
Branch: v4.2
https://github.com/mongodb/mongo/commit/b1696afb660609b0943350f21146b30d676c9dee

Comment by Justin Seyster [ 11/Jun/19 ]

We should backport this so it doesn't continue to cause test failures.

Comment by Githook User [ 11/Jun/19 ]

Author:

{'name': 'Justin Seyster', 'email': 'justin.seyster@mongodb.com', 'username': 'jseyster'}

Message: SERVER-41589 OplogStartHack should use the requested yield policy.
Branch: master
https://github.com/mongodb/mongo/commit/86b07826cede4cfd33e1a47f10a111b1d96e9758

Generated at Thu Feb 08 04:58:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.