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

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Aggregation Framework
    • None
    • Query
    • Fully Compatible
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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'.

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

              Created:
              Updated:
              Resolved: