[SERVER-45370] Test scenarios where multiple transactions try to create the same collection Created: 06/Jan/20  Updated: 29/Oct/23  Resolved: 24/Jan/20

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

Type: Task Priority: Major - P3
Reporter: Maria van Keulen 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
depends on SERVER-45650 Do not std::terminate() if _commitSto... Closed
Related
related to SERVER-57928 create_collection.js should use a de... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2020-01-13, Execution Team 2020-01-27
Participants:

 Description   

These scenarios should include one where one transaction commits and the other aborts, and one where both transactions commit. In the case where both commit, the second to commit should fail, since the collection already exists.



 Comments   
Comment by Githook User [ 24/Jan/20 ]

Author:

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

Message: SERVER-45370 Fix oplog hole and test parallel createCollection txns

Testing parallel transactions with createCollections found a hang
scenario caused by reserving oplog slots before transaction commit.
This patch adds this testing and fixes this bug.
Branch: master
https://github.com/mongodb/mongo/commit/cc39f69e7b2d79a3074a546ca33d30a0307bc238

Comment by Maria van Keulen [ 23/Jan/20 ]

This ticket is now un-blocked since SERVER-45650 is in.

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