[SERVER-38105] Remove uassertLockTimeout Created: 13/Nov/18 Updated: 29/Oct/23 Resolved: 31/May/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | 4.0.4 |
| Fix Version/s: | 4.1.14 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Gabriel Villasana (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Execution Team 2019-06-03 |
| Participants: |
| Description |
|
It appears that the catalog RAII objects will construct a string with the resource name intended for error reporting regardless of whether error reporting needs to be done or not. This is kind of wasteful and can easily be fixed by just passing the resource id instead and only constructing a string in the uassert statement. In addition, there is a string copy on this line. |
| Comments |
| Comment by Githook User [ 31/May/19 ] |
|
Author: {'name': 'Gabe Villasana', 'email': 'gabe.villasana@mongodb.com'}Message: |
| Comment by Eric Milkie [ 15/Apr/19 ] |
|
It now appears there are no callers of uassertLockTimeout(); therefore, I changed the title to just be that we should remove that dead function. |