[SERVER-45632] Some fuzzer tests does not have the transactionLifetimeLimitSeconds parameter Created: 17/Jan/20  Updated: 29/Oct/23  Resolved: 11/Mar/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 4.3.2
Fix Version/s: 4.4.0-rc0, 4.7.0

Type: Bug Priority: Major - P3
Reporter: Marcos José Grillo Ramirez Assignee: Max Hirschhorn
Resolution: Fixed Votes: 0
Labels: sharding-4.4-stabilization, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4
Sprint: Sharding 2020-03-23
Participants:
Linked BF Score: 44

 Description   

Some transaction fuzzer tests does not have the transactionLifetimeLimitSeconds parameter set on the config file like other tests. This causes the test to run on the default value which causes a timed out if the fuzzer generated a test that never commits a transaction.



 Comments   
Comment by Githook User [ 10/Mar/20 ]

Author:

{'name': 'Max Hirschhorn', 'username': 'visemet', 'email': 'max.hirschhorn@mongodb.com'}

Message: SERVER-45632 Set transactionLifetimeLimitSeconds in jstestfuzz_sharded*

(cherry picked from commit bdccd869c1a5465271cb011368c3321b7c3abb0b)
Branch: v4.4
https://github.com/mongodb/mongo/commit/119898735de1c741f3f9f4dfde1abf251f1c9faa

Comment by Githook User [ 10/Mar/20 ]

Author:

{'name': 'Max Hirschhorn', 'username': 'visemet', 'email': 'max.hirschhorn@mongodb.com'}

Message: SERVER-45632 Set transactionLifetimeLimitSeconds in jstestfuzz_sharded*
Branch: master
https://github.com/mongodb/mongo/commit/bdccd869c1a5465271cb011368c3321b7c3abb0b

Comment by Max Hirschhorn [ 10/Mar/20 ]

The reason why the jstestfuzz_sharded.yml and jstestfuzz_sharded_session.yml test suites weren't setting the transactionLifetimeLimitSeconds=1 is because they're still running with stand-alone shards (SERVER-43927) and aren't expecting multi-statement transactions to succeed. However, the generated jstestfuzz_sharded_multiversion.json task configuration uses jstestfuzz_sharded.yml as its base and additionally specifies --numReplSetNodes via the command line, which causes replica set shards to be used. It's harmless to set transactionLifetimeLimitSeconds=1 for a stand-alone mongod that we can do it now independently of always using replica set shards.

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