[SERVER-21749] $lookup should obey maxTimeMS Created: 02/Dec/15  Updated: 05/Feb/16  Resolved: 11/Dec/15

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

Type: Bug Priority: Major - P3
Reporter: Charlie Swanson Assignee: Charlie Swanson
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: QuInt D (12/14/15)
Participants:

 Description   

The maxTimeMS option of the aggregate command is not passed to the sub-query of the $lookup stage, so it proceeds as if there was no timeout specified.



 Comments   
Comment by Githook User [ 11/Dec/15 ]

Author:

{u'username': u'cswanson310', u'name': u'Charlie Swanson', u'email': u'charlie.swanson@mongodb.com'}

Message: SERVER-21749 Ensure $lookup obeys maxTimeMS limit

The $lookup stage uses a DBDirectClient to do its queries, which shares
the same OperationContext as the aggregation pipeline, but does not
share the CurOp, so does not inherit the time limit. To ensure a query
started this way obeys the maxTimeMS limit, a newly constructed CurOp
should inspect the OperationContext to calculate its remaining time.
Branch: master
https://github.com/mongodb/mongo/commit/3191dbe15c70f1eb6546260d61fe9b0c7d10e045

Generated at Thu Feb 08 03:58:18 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.