[SERVER-35263] Add FSM workloads for testing atomicity and isolation of updates inside a transaction across multiple collections and databases Created: 27/May/18  Updated: 29/Oct/23  Resolved: 27/Jun/18

Status: Closed
Project: Core Server
Component/s: Replication, Testing Infrastructure
Affects Version/s: None
Fix Version/s: 4.0.1, 4.1.1

Type: Task Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Robert Guo (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
depends on SERVER-34293 Add FSM workload for testing atomicit... Closed
Problem/Incident
Related
related to SERVER-35852 Convert backup_restore.js blacklist t... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.0
Sprint: TIG 2018-06-18, TIG 2018-07-02
Participants:
Linked BF Score: 12
Story Points: 2

 Description   

Extend the multi_statement_transaction_atomicity_isolation.js FSM workload from SERVER-34293 to support running the updates and consistency checks against collections or databases specified via $config.data. The multi_statement_transaction_atomicity_isolation.js FSM workload should continue to only run against the db[collName] collection provided by the concurrency framework.



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

Author:

{'username': 'guoyr', 'name': 'Robert Guo', 'email': 'robert.guo@10gen.com'}

Message: SERVER-35263 add FSM workload for testing txns across multiple DBs

(cherry picked from commit 4c77f4f5a72a27ac98557de49b74eb1a019dd196)
Branch: v4.0
https://github.com/mongodb/mongo/commit/811d781d436df806e9fa0c57b0c98960cf2cc12e

Comment by Robert Guo (Inactive) [ 27/Jun/18 ]

Author:

{'username': 'guoyr', 'name': 'Robert Guo', 'email': 'robert.guo@10gen.com'}

Message: SERVER-35263 blacklist test from backup_restore.js
Branch: master
https://github.com/mongodb/mongo/commit/f0f2530e83db70d89a12298a25ba2cde35cf0990

Comment by Max Hirschhorn [ 24/Jun/18 ]

I'm reopening this ticket to address the failure from BF-9678. We need to avoid running the multi_statement_transaction_atomicity_isolation_multi_db.js FSM workload in the backup_restore*.js tests. I think we should separately look to convert the blacklist to a YAML-based exclude_with_any_tags for "uses_transactions" so we don't have to remember to do this every time a new multi-statement transaction FSM workload is added.

Comment by Githook User [ 19/Jun/18 ]

Author:

{'username': 'guoyr', 'name': 'Robert Guo', 'email': 'robert.guo@10gen.com'}

Message: SERVER-35263 add FSM workload for testing txns across multiple DBs
Branch: master
https://github.com/mongodb/mongo/commit/4c77f4f5a72a27ac98557de49b74eb1a019dd196

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