[SERVER-56112] [SBE] Remove redundant oplog locking in TransactionHistoryIterator::next() path Created: 15/Apr/21 Updated: 27/Oct/23 Resolved: 23/Jun/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Query Execution |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mindaugas Malinauskas | Assignee: | Backlog - Query Execution |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | sbe-post-v1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Execution
|
||||||||
| Participants: | |||||||||
| Description |
|
When SBE is on, in TransactionHistoryIterator::next() oplog lock is acquired in findOneOplogEntry() and by SBE in ScanStage. Remove the redundant oplog locking. |
| Comments |
| Comment by David Storch [ 23/Jun/21 ] |
|
The redundant locking described here no longer exists due to the changes made in Closing this ticket as "Gone Away". |