[SERVER-31841] mongo_lock's find_mutex_holder should handle mutexes with no apparent holder Created: 06/Nov/17 Updated: 30/Oct/23 Resolved: 19/Dec/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Eddie Louie |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | TIG 2018-1-1, TIG 2017-12-18 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
In mongo_lock.py, find_mutex_holder() looks up a mutex holder in a thread_dict map, but doesn't check for the key's existence first. If the key doesn't exist, the entire MongoDBDumpLocks run fails with a backtrace and this Python error message:
Instead, it should simply print an informative message and continue. |
| Comments |
| Comment by Githook User [ 19/Dec/17 ] |
|
Author: {'name': 'Eddie Louie', 'email': 'eddie.louie@mongodb.com', 'username': 'elouie99'}Message: |