[SERVER-45135] WTCheckpointThread throws LockTimeout when 'failNonIntentLocksIfWaitNeeded' is enabled and the CheckpointLock is held by another thread Created: 13/Dec/19 Updated: 29/Oct/23 Resolved: 17/Dec/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Wlodarek | Assignee: | Gregory Wlodarek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Execution Team 2019-12-16 | ||||
| Participants: | |||||
| Linked BF Score: | 48 | ||||
| Description |
|
The 'failNonIntentLocksIfWaitNeeded' fail point will immediately throw a LockTimeout exception even if the deadline is set to Date_t::max() when the WTCheckpointThread cannot immediately acquire the CheckpointLock because another thread is holding it. This is only happening on the fuzzer because it enables that fail point. |
| Comments |
| Comment by Githook User [ 17/Dec/19 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |