[SERVER-38025] Remove uses_transactions tag blacklist from concurrency sharded suites without failovers Created: 08/Nov/18  Updated: 29/Oct/23  Resolved: 05/Dec/18

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

Type: Task Priority: Major - P3
Reporter: Jack Mulrow Assignee: Jack Mulrow
Resolution: Fixed Votes: 0
Labels: ShardedTxn:Testing
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-34570 Remove isSharded() checks from FSM tr... Closed
Gantt Dependency
has to be done after SERVER-38094 Send prepareTransaction with write co... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-11-19, Sharding 2018-12-03, Sharding 2018-12-17
Participants:

 Description   

Currently the various concurrency_sharded... suites blacklist any tests that use transactions. Now that transactions are supported in sharded clusters without failovers, these tests can be unblacklisted.



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

Author:

{'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}

Message: SERVER-38025 Run transaction workloads in sharded concurrency suites w/o failovers or causal consistency
Branch: master
https://github.com/mongodb/mongo/commit/0e3cd046441e8ba1427068ef8d6dbaae4c8cefd3

Comment by Jack Mulrow [ 08/Nov/18 ]

Yeah, good catch. I updated the title and closed SERVER-34570 as a duplicate.

Comment by Max Hirschhorn [ 08/Nov/18 ]

Remove requires_sharding tag blacklist from concurrency sharded suites without failovers

jack.mulrow, I think you mean the uses_transaction tag. We should also close one of SERVER-34570 or this ticket.

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