[SERVER-34704] Write test for transactions on collections that are renamed concurrently Created: 26/Apr/18  Updated: 29/Oct/23  Resolved: 05/Jun/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.0.0-rc5, 4.1.1

Type: Task Priority: Minor - P4
Reporter: William Schultz (Inactive) Assignee: Tess Avitabile (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
is related to SERVER-34652 Write tests for transactions that wri... Closed
is related to SERVER-34703 Write test for transactions with conc... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.0
Sprint: Repl 2018-05-21, Repl 2018-06-04, Repl 2018-06-18
Participants:
Story Points: 1

 Description   

We want to test the interaction of transactions and collection renames. We should test cases where a transactions writes to a collection A that is concurrently renamed to B. We should verify the renameCollection blocks until the transaction commits or until maxTimeMS expires. We should test this when A and B are in the same database and when they are in different databases.



 Comments   
Comment by Githook User [ 05/Jun/18 ]

Author:

{'username': 'tessavitabile', 'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com'}

Message: SERVER-34652 SERVER-34654 SERVER-34703 SERVER-34704 Test transactions with concurrent DDL operations

(cherry picked from commit 14ffe1360e095d98da824bb63417672f3b171270)
Branch: v4.0
https://github.com/mongodb/mongo/commit/00c01f088742a70bd93843d0dac5900c64e97b98

Comment by Githook User [ 05/Jun/18 ]

Author:

{'username': 'tessavitabile', 'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com'}

Message: SERVER-34652 SERVER-34654 SERVER-34703 SERVER-34704 Test transactions with concurrent DDL operations
Branch: master
https://github.com/mongodb/mongo/commit/14ffe1360e095d98da824bb63417672f3b171270

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