Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-86168

maxTimeAlwaysTimeOut failpoint should not apply to internal commands.

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • QE 2024-03-04, QE 2024-03-18, QE 2024-04-01, QE 2024-04-15, QE 2024-04-29, QE 2024-05-13, QE 2024-05-27, QE 2024-06-10, QE 2024-06-24, QE 2024-07-08, QE 2024-07-22, QE 2024-08-05, QE 2024-08-19, QE 2024-09-02, QE 2024-09-16, QE 2024-09-30, QE 2024-10-14, QE 2024-10-28, QE 2024-11-11, QE 2024-11-25
    • 12

      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.

            Assignee:
            parker.felix@mongodb.com Parker Felix
            Reporter:
            parker.felix@mongodb.com Parker Felix
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: