[SERVER-36121] Determine how transactionLifetimeLimitSeconds parameter works against mongos Created: 13/Jul/18  Updated: 29/Oct/23  Resolved: 04/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: Randolph Tan
Resolution: Fixed Votes: 0
Labels: ShardedTxn:Testing, todo_in_code
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-43489 Remove TODO SERVER-36121 Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-12-03, Sharding 2018-12-17
Participants:

 Description   

Some core/txns tests set transactionLifetimeLimitSeconds, but they can't currently be run in the sharded core txns suite because mongos doesn't have this parameter.

The tests are:

  • jstests/core/txns/abort_expired_transaction.js
  • jstests/core/txns/abort_transaction_thread_does_not_block_on_locks.js


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

Author:

{'name': 'Randolph Tan', 'email': 'randolph@10gen.com', 'username': 'renctan'}

Message: SERVER-36121 Add transaction expiration jstests for sharded clusters
Branch: master
https://github.com/mongodb/mongo/commit/fdf55fe183a07114428c69f091c94800ed9f3dac

Comment by Randolph Tan [ 14/Nov/18 ]

Based on discussion, we should probably make a sharded version of these tests and set the parameter to the shards directly.

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