[SERVER-38018] Unblacklist multi_statement_transaction_all_commands.js in concurrency_simultaneous_replication test Created: 07/Nov/18  Updated: 29/Oct/23  Resolved: 19/Mar/19

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

Type: Task Priority: Major - P3
Reporter: Siyuan Zhou Assignee: Siyuan Zhou
Resolution: Fixed Votes: 0
Labels: open_todo_in_code
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-37841 multi_statement_transaction_all_comma... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2018-12-03, Repl 2018-12-17, Repl 2019-01-14, Repl 2019-01-28, Repl 2019-02-11, Repl 2019-02-25, Repl 2019-03-11, Repl 2019-03-25
Participants:

 Description   

Due to SERVER-37841, multi_statement_transaction_all_commands.js implicitly aborts transactions. When glabal writer lock is enqueued after a running transaction, higher txnNumber will block while waiting for read concern's afterClusterTime, since it needs the lock to access the oplog collection. Waiting for read concern is moved to before implicitly aborting transaction by SERVER-37179.

Once SERVER-37841 is done, we can unblacklist it in concurrency_simultaneous_replication.

Additionally, until SERVER-37199 is fixed, multi_statement_transaction_atomicity_isolation_metrics_test.js is also blacklisted in the concurrency_simultaneous_replication test due to a deadlock caused by secondary application of prepared transactions. This ticket should also unblacklist multi_statement_transaction_atomicity_isolation_metrics_test.js once this is fixed.



 Comments   
Comment by Githook User [ 19/Mar/19 ]

Author:

{'name': 'Siyuan Zhou', 'username': 'visualzhou', 'email': 'siyuan.zhou@mongodb.com'}

Message: SERVER-38018 Unblacklist multi_statement_transaction_all_commands.js in concurrency_simultaneous_replication test
Branch: master
https://github.com/mongodb/mongo/commit/81d045a17ddf08e9f0eb7f30f96b45a352fab5cc

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