[SERVER-42439] Parameterize 'failNonIntentLocksIfWaitNeeded' failpoint with optional timeout Created: 25/Jul/19 Updated: 02/Aug/19 Resolved: 02/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Vesselina Ratcheva (Inactive) | Assignee: | Vesselina Ratcheva (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Repl 2019-08-12 | ||||||||
| Participants: | |||||||||
| Description |
|
This is useful for giving the affected lock acquisitions a chance in the face of temporary delays (e.g. HMAC). If this new optional timeout parameter is set, instead of failing the acquisition immediately, we override the timeout that the lock would normally have. Users of this failpoint can set this timeout to a low value in order to avoid unintended lock failures without holding up the test for too long. See here. |
| Comments |
| Comment by Vesselina Ratcheva (Inactive) [ 02/Aug/19 ] |
|
Closing in favor of |