[SERVER-31261] Improve diagnosibility of long running transactions in OperationContext Created: 26/Sep/17 Updated: 06/Dec/22 Resolved: 25/May/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | SWDI | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
One idea: (Debug mode only) Start a timer when a txn starts; when txn ends, if the timer expires, log a message. |
| Comments |
| Comment by Geert Bosch [ 30/Mar/18 ] | ||
|
Given that, it seems this is a duplicate. | ||
| Comment by Ian Whalen (Inactive) [ 16/Mar/18 ] | ||
|
geert.bosch can you please speak to bruce.lucas to confirm where this should go before we bounce it to another team? | ||
| Comment by Ian Whalen (Inactive) [ 16/Mar/18 ] | ||
|
Sorry for the hot potato but bouncing to Repl since this is a request for the not-yet-released transactions work. | ||
| Comment by Bruce Lucas (Inactive) [ 26/Sep/17 ] | ||
|
Maybe the max transaction time for an operation could be recorded logged as part of slow query logging? For very long transactions that may not complete, e.g. because they are hung or because they cause a hang by getting the cache stuck full, possibly a message could be logged say every 10 seconds that a transaction is open. Normally you wouldn't want to log anything while holding a transaction, but if the transaction has been going 10 seconds logging a message may not make it particularly worse. The above would be for normal operation, not just debug mode, to help diagnose these issues in the field. |