[SERVER-26321] Long-running aggregations can artificially time out if the first batch takes more than 10 minutes Created: 26/Sep/16  Updated: 06/Dec/22  Resolved: 19/May/17

Status: Closed
Project: Core Server
Component/s: Aggregation Framework
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Ian Whalen (Inactive) Assignee: Backlog - Query Team (Inactive)
Resolution: Duplicate Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-28327 ClientCursorMonitor can timeout curso... Closed
Related
related to SERVER-28942 sort by shard key or prefix of shard ... Backlog
is related to SERVER-6036 Disable cursor timeout for cursors th... Closed
Assigned Teams:
Query
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:
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'.


Generated at Thu Feb 08 04:11:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.