[SERVER-61122] Log TxnNumberAndRetryCounter in metrics and log methods inside TransactionParticipant and TransactionRouter Created: 29/Oct/21 Updated: 29/Oct/23 Resolved: 25/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.6 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jason Zhang | Assignee: | Sanika Phanse (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2022-01-24, Sharding 2022-02-07 |
| Participants: | |
| Story Points: | 1 |
| Description |
|
Specifically in the currentOp and slow log output. Additionally, we should include the txnRetryCounter in the logv2 log lines in the TransactionRouter where we currently log txnNumber and in the txnId string. |
| Comments |
| Comment by Githook User [ 24/Jan/22 ] |
|
Author: {'name': 'Sanika Phanse', 'email': 'sanika.phanse@mongodb.com', 'username': 'sphanse99'}Message: |