[SERVER-86168] maxTimeAlwaysTimeOut failpoint should not apply to internal commands. Created: 02/Feb/24 Updated: 03/Feb/24 |
|
| Status: | Needs Scheduling |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Parker Felix | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Execution
|
||||||||
| Participants: | |||||||||
| Linked BF Score: | 12 | ||||||||
| Description |
|
The maxTimeAlwaysTimeOut failpoint should either only apply to external commands or the user of the failpoint should explicitly specify which commands they want to time out. The current usage of this failpoint appears to only be for specific external commands that they want to timeout, so this change shouldn't need to break existing usage. |