[SERVER-39917] Increase transactionLifetimeLimitSeconds in transactions_reaped_with_tickets_exhausted.js Created: 01/Mar/19  Updated: 29/Oct/23  Resolved: 05/Mar/19

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

Type: Bug Priority: Major - P3
Reporter: William Schultz (Inactive) Assignee: William Schultz (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2019-03-11
Participants:
Linked BF Score: 35

 Description   

The transactions_reaped_with_tickets_exhausted.js starts a transaction and then runs several collection 'drop' commands on the same database which are expected to block behind the transaction. Then, the test tries to run another operation on the transaction which it expects to block behind the collection drops and eventually time out due to the transaction expiring and being reaped. At the beginning of the test, it sets transactionLifetimeLimitSeconds to 5 seconds, so that the second operation on the transaction will eventually fail when the transaction is reaped. This timeout is low enough that sometimes the transaction will get reaped before the collection drop commands are started, causing the test to erroneously fail. We should either increase this timeout or make the test resilient to timing differences on various hosts.



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

Author:

{'name': 'William Schultz', 'email': 'william.schultz@mongodb.com', 'username': 'will62794'}

Message: SERVER-39917 Increase transactionLifetimeLimitSeconds in transactions_reaped_with_tickets_exhausted.js to 20 seconds
Branch: master
https://github.com/mongodb/mongo/commit/34d1fe760ca8dd8752c379dbce4b897b148bbc0a

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