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

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Aggregation Framework
    • None
    • Query
    • Fully Compatible
    • ALL
    • None
    • 3
    • 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 - Query Team (Inactive)
              Reporter:
              Ian Whalen (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: