[SERVER-35168] Track information about last client to run a transaction operation on session Created: 22/May/18 Updated: 29/Oct/23 Resolved: 13/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-30 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
To support the currentOp output for inactive transactions, we want to keep track of information about the last client to run an operation against a particular session. Normally, a single operation in currentOp (not a transaction) is only associated with a single client. For sessions (and transactions), though, it is possible that different clients run operations against a single session. Often, all operations will be run by the same client, and so it would be helpful to store this information on the session, so we can report it in currentOp. The information we hope to store about the last client is connectionId, client, appName, and clientMetadata. |
| Comments |
| Comment by Githook User [ 15/Aug/18 ] |
|
Author: {'username': 'jinichu', 'email': 'jinnybyun@gmail.com', 'name': 'jinichu'}Message: (cherry picked from commit cf1f02c116a9f28b97bc6c41148446342349785c) |
| Comment by Githook User [ 13/Jul/18 ] |
|
Author: {'username': 'jinichu', 'name': 'jinichu', 'email': 'jinnybyun@gmail.com'}Message: |
| Comment by William Schultz (Inactive) [ 06/Jun/18 ] |
|
See linked dependent ticket. |
| Comment by Tess Avitabile (Inactive) [ 06/Jun/18 ] |
|
Should we also add this to the currentOp output for inactive transactions as part of this work? Or is that in another ticket? |