[SERVER-77538] Restore from yield fails if collection is still marked uncommitted Created: 26/May/23  Updated: 29/Oct/23  Resolved: 25/Jul/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 7.0.0-rc2
Fix Version/s: 7.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Henrik Edin Assignee: Gregory Wlodarek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-79309 Port SERVER-77538 to Shard Role acqui... Closed
Assigned Teams:
Storage Execution
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution NAMR Team 2023-06-26, Execution NAMR Team 2023-07-24, Execution NAMR Team 2023-08-07
Participants:
Linked BF Score: 5

 Description   

Queries may start in the window where a new Collection is committed to WT but not yet committed into the local catalog if they can observe the collection from the opened snapshot.

When queries restore after yield, they perform a lookup by UUID to restore the collection. If the thread that added the collection still hasn't executed its commit handlers (where the collection is marked as committed) the restore from yield will fail.



 Comments   
Comment by Githook User [ 25/Jul/23 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-77538 Fix restore from yield if the collection is still marked uncommitted
Branch: master
https://github.com/mongodb/mongo/commit/7488e36263e0186d6ad67d3488d790eca669bbcd

Comment by Daniel Gomez Ferro [ 31/May/23 ]

Does this also affect the new acquisitions?

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