maxTimeMs not respected for delay in query optimization

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.0-rc0
    • Affects Version/s: 7.0.0, 8.1.0-rc0, 8.0.0
    • Component/s: None
    • None
    • Query Execution
    • Fully Compatible
    • ALL
    • QE 2025-03-17, QE 2025-03-31, QE 2025-04-14
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      If at some point before query execution we encounter a delay that exceeds the maxTimeMs set on a query, the query won't be killed; instead the query will be allowed to execute to completion & we may even get a slow-query log after.

      Note that if the query was issued on a sharded cluster, the router will correctly detect the timeout/ cancel the operation; however, the mongod will continue to execute the query past the timeout.

              Assignee:
              Mickey Winters
              Reporter:
              Alya Berciu
              Votes:
              0 Vote for this issue
              Watchers:
              16 Start watching this issue

                Created:
                Updated:
                Resolved: