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

Long-running aggregations can artificially time out if the first batch takes more than 10 minutes

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Aggregation Framework
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Case:

      Description

      The ClientCursor created to hold the results of the aggregation will be created before we construct the first batch. Once constructed, it will start tracking its _idleAgeMillis, even though the cursor is not yet 'idle'.

        Attachments

          Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. SERVER-28327 ClientCursorMonitor can timeout cursors prematurely

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-6036 Disable cursor timeout for cursors that belong to a session

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-28942 sort by shard key or prefix of shard key may not require merge before group

          • Major - P3 - Major loss of function.
          • Open

            Activity

              People

              Assignee:
              backlog-server-query Backlog - Query Team (Inactive)
              Reporter:
              ian.whalen Ian Whalen
              Participants:
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: