[SERVER-39985] Improve transaction lock failure error message Created: 06/Mar/19 Updated: 29/Oct/23 Resolved: 26/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Bruce Lucas (Inactive) | Assignee: | Gregory Wlodarek |
| Resolution: | Fixed | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Sprint: | Execution Team 2019-07-01 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||
| Description |
|
The error message when a transaction statement is unable to acquire a lock within the timeout is cryptic, making it difficult to identify the conflicting operation:
Would it be possible to include more information that could help pinpoint the cause of the conflict, for example
|
| Comments |
| Comment by Githook User [ 26/Jun/19 ] |
|
Author: {'name': 'Gregory Wlodarek', 'username': 'GWlodarek', 'email': 'gregory.wlodarek@mongodb.com'}Message: |
| Comment by Gregory Wlodarek [ 21/Jun/19 ] |
|
I'll look at the remaining requests in this ticket. |