[SERVER-36414] Add readConcern to slow transaction logging Created: 02/Aug/18  Updated: 29/Oct/23  Resolved: 03/Aug/18

Status: Closed
Project: Core Server
Component/s: Diagnostics, Replication
Affects Version/s: None
Fix Version/s: 4.0.2, 4.1.2

Type: Task Priority: Major - P3
Reporter: Jinny Byun Assignee: Jinny Byun
Resolution: Fixed Votes: 0
Labels: per-txn-metrics
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-35433 Log slow transactions when they finish Closed
Backwards Compatibility: Fully Compatible
Participants:

 Description   

Currently, Session::_logSlowTransaction() doesn't log the transaction's readConcern. We should add the transaction's readConcern as part of this logging function, and fetch the readConcern from either the OperationContext orĀ _txnResourceStash.



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

Author:

{'username': 'jinichu', 'email': 'jinnybyun@gmail.com', 'name': 'jinichu'}

Message: SERVER-36414 Add readConcern to slow transaction logging

(cherry picked from commit 17f64a621f5dc1431e663bdaa46208432f67c441)
Branch: v4.0
https://github.com/mongodb/mongo/commit/562d076100007c2b130ce4b6f9ec9740463bba7b

Comment by Githook User [ 03/Aug/18 ]

Author:

{'username': 'jinichu', 'name': 'jinichu', 'email': 'jinnybyun@gmail.com'}

Message: SERVER-36414 Add readConcern to slow transaction logging
Branch: master
https://github.com/mongodb/mongo/commit/17f64a621f5dc1431e663bdaa46208432f67c441

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