[SERVER-61819] Fix bug in SBE around capped collections and (new) yielding Created: 30/Nov/21  Updated: 29/Oct/23  Resolved: 05/Jan/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.3.0

Type: Bug Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Ian Boros
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2021-12-27, Execution Team 2022-01-10
Participants:

 Description   

It's possible for the SBE Scan stage to yield (with the new behavior gated by a feature flag) and lose its position on a capped position without returning a CappedPositionLost error.



 Comments   
Comment by Githook User [ 05/Jan/22 ]

Author:

{'name': 'Ian Boros', 'email': 'ian.boros@mongodb.com', 'username': 'borosaurus'}

Message: SERVER-61819 Fix SBE yielding bug around capped collections

Previously, if SBE was reading from a capped collection, it was possible
to fall off the capped collection without returning a CappedPositionLost
error.
Branch: master
https://github.com/mongodb/mongo/commit/e1a3d63d9753d6922b36335603f37eb6cbb89c3f

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