[SERVER-17680] Improve maxTimeMS test coverage with aggregation framework Created: 20/Mar/15  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Aggregation Framework, Querying
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: J Rassi Assignee: Backlog - Query Execution
Resolution: Unresolved Votes: 0
Labels: PM-265, maxTimeMS
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Query Execution
Participants:

 Description   

The following uses of maxTimeMS are not currently covered by jstests, but should be:

  • Test that mongod properly sets the leftover time on the aggregation cursor, if a cursor needs to be saved for getMore.
  • Test that mongos properly propagates maxTimeMS to the shards (for an aggregation on a sharded collection).
  • Test that mongos properly propagates maxTimeMS to the primary shard for the merge operation (for an aggregation on a sharded collection).

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