[SERVER-44138] Stash UncommittedCollections resources with other transaction state Created: 21/Oct/19  Updated: 29/Oct/23  Resolved: 19/Dec/19

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

Type: New Feature Priority: Major - P3
Reporter: Geert Bosch Assignee: Maria van Keulen
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-44139 Allow collection creation inside a mu... Closed
Related
related to SERVER-45256 Complete TODO listed in SERVER-44138 Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2019-11-04, Execution Team 2019-11-18, Execution Team 2019-12-16, Execution Team 2019-12-30
Participants:

 Description   

As of SERVER-43859, we have a registry of pending collections (UncommittedCollections) as a decoration on the OperationContext. AutoGetCollection performs collection name lookups starting with the UncommittedCollections registry. The collections in the registry are committed via the RecoveryUnit's onCommit handler, and cleared via the onRollback handler.

This ticket should allow for these UncommittedCollections to be stashed along with other transaction state.

This ticket needs a unit test, but feel free to defer that to a new ticket.



 Comments   
Comment by Githook User [ 18/Dec/19 ]

Author:

{'name': 'Maria van Keulen', 'email': 'maria.vankeulen@mongodb.com', 'username': 'mvankeulen94'}

Message: SERVER-44138 Stash uncommitted collections with other transaction state
Branch: master
https://github.com/mongodb/mongo/commit/cf4daadf45ced157fd347480f046f8b5a58f05fa

Comment by Maria van Keulen [ 16/Dec/19 ]

We believe it should be sufficient to keep UncommittedCollections as a decoration on the OperationContext for SERVER-44139, provided that they are stashed along with other transaction state. I've updated the ticket description and title to reflect this.

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