[SERVER-34486] Set transactionLifetimeLimitSeconds=1 in the fuzzer suites that run with replication enabled Created: 15/Apr/18  Updated: 29/Oct/23  Resolved: 30/Apr/18

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 4.0.0-rc0

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:
Depends
depends on SERVER-33295 Kill long-running snapshot transactions Closed
Gantt Dependency
Backwards Compatibility: Fully Compatible
Sprint: TIG 2018-05-07
Participants:
Story Points: 1

 Description   

mongod_options:
  set_parameters:
    transactionLifetimeLimitSeconds: 1

should be added to the following test suites in order to avoid having the fuzzer trigger spurious Evergreen timeouts when it goes to wait for itself to be able to take a non-intent lock after having started a transaction.

  • jstestfuzz_interrupt_replication.yml
  • jstestfuzz_replication.yml
  • jstestfuzz_replication_initsync.yml
  • jstestfuzz_replication_session.yml
  • jstestfuzz_sharded_causal_consistency.yml (uses replica set shards)
  • jstestfuzz_sharded_continuous_stepdown.yml (uses replica set shards)


 Comments   
Comment by Githook User [ 30/Apr/18 ]

Author:

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

Message: SERVER-34486 Set transactionLifetimeLimitSeconds=1 in the fuzzer suites that run with replication enabled
Branch: master
https://github.com/mongodb/mongo/commit/1f68e5807f34985a8d1abcb41acd6b3666ef8d13

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