[SERVER-38470] Add more logging to TransactionRouter Created: 07/Dec/18  Updated: 29/Oct/23  Resolved: 16/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: Jack Mulrow
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-12-17
Participants:
Linked BF Score: 14

 Description   

More logging in the TransactionRouter (at a high verbosity level) would make diagnosing failures easier, particularly while sharded transactions are being stabilized. A few things that could be logged:

  1. Starting / continuing a transaction
  2. Contacting new / existing participant shard
  3. Resetting state on stale version, snapshot, or view resolution error
  4. Committing / aborting a transaction


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

Author:

{'username': 'jsmulrow', 'email': 'jack.mulrow@mongodb.com', 'name': 'Jack Mulrow'}

Message: SERVER-38470 Add more logging to TransactionRouter
Branch: master
https://github.com/mongodb/mongo/commit/2d94c21d3af7d4b4fc32e6c34791ac24a2a35c0a

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