[SERVER-35434] Track aggregate OpDebug stats in SingleTransactionStats Created: 05/Jun/18 Updated: 29/Oct/23 Resolved: 09/Jul/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics, Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.2, 4.1.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | William Schultz (Inactive) | 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: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Backport Requested: |
v4.0
|
||||||||||||||||
| Sprint: | Repl 2018-07-02, Repl 2018-07-16 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
We want to track aggregate operation stats inside SingleTransactionsStats using an OpDebug object that accumulates stats from all operations run inside a transaction. We should have an OpDebug member variable on SingleTransactionStats, and we should add to it the stats from the latest operation whenever that operation finishes i.e. whenever a transaction operation stashes its resources, we will add its CurOp::_debug field to the aggregate OpDebug instance stored in the SingleTransactionsStats instance on the session. |
| Comments |
| Comment by Githook User [ 15/Aug/18 ] |
|
Author: {'username': 'jinichu', 'email': 'jinnybyun@gmail.com', 'name': 'jinichu'}Message: (cherry picked from commit f7dbf6f03397ef6317d8e9dc7bbb32e41a0745d1) |
| Comment by Githook User [ 09/Jul/18 ] |
|
Author: {'username': 'jinichu', 'name': 'jinichu', 'email': 'jinnybyun@gmail.com'}Message: |