[SERVER-59677] Remove stale comment from plan_yield_policy.cpp Created: 30/Aug/21  Updated: 29/Oct/23  Resolved: 23/Jun/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.1.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Ian Boros Assignee: Jeffrey Xiao
Resolution: Fixed Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: QE 2021-09-20, QE 2021-10-04, QE 2021-10-18, Execution Team 2021-11-15, Execution Team 2021-11-29, Execution Team 2021-12-13, Execution Team 2021-12-27, Execution Team 2022-01-10, Execution Team 2022-01-24, Execution Team 2022-02-07
Participants:

 Description   

This comment is out of date:

    // A yield has occurred, but there still may not be a 'yieldable'. This is true, for example,
    // when executing a getMore for the slot-based execution engine. SBE uses the "locks internally"
    // lock policy, and therefore the getMore code path does not acquire any db_raii object. As a
    // result, there is no db_raii object to restore here when executing a getMore against a cursor
    // using SBE.

SBE now takes locks outside of the plan.



 Comments   
Comment by Githook User [ 16/Jun/22 ]

Author:

{'name': 'Jeffrey Xiao', 'email': 'jeffrey.xiao@mongodb.com', 'username': 'jxiao'}

Message: SERVER-59677 Remove stale comment
Branch: master
https://github.com/mongodb/mongo/commit/29801279ed59068602d2961cafa2193c3e477879

Comment by Ian Boros [ 30/Aug/21 ]

Normally I would just fix this myself and put it in CR but this may be a good warmup ticket for someone.

Generated at Thu Feb 08 05:47:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.