[SERVER-35298] Profiling transaction operations should always succeed Created: 30/May/18 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Querying, Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Backlog - Replication Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Replication
|
||||||||
| Participants: | |||||||||
| Description |
|
Currently its possible for an operation in a transaction to complete successfully, but no profiling entry for that operation to be written, even if the op should have been profiled based on the duration of the op and the current profiler configuration. The profile entry can fail to be written if there's any contention grabbing the lock on the system.profile collection, or if the operation gets killed after it has completed but before it has been profiled. |