[SERVER-15652] SubplanStage and MultiPlanStage plan selection should be non-blocking Created: 14/Oct/14  Updated: 02/Aug/18  Resolved: 21/Oct/14

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: 2.7.8
Fix Version/s: 2.7.8

Type: Task Priority: Major - P3
Reporter: Samantha Ritter (Inactive) Assignee: David Storch
Resolution: Done Votes: 0
Labels: 28qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-15651 GroupStage work should be non-blocking Closed
Tested
Participants:

 Description   

SuplanStage selects a plan in a single call to pickBestPlan(), which does a hefty amount of work. This method is blocking, it should be done in yield-able units of work.



 Comments   
Comment by Githook User [ 27/Oct/14 ]

Author:

{u'username': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}

Message: SERVER-15652: for parallel collection scan, make sure we call saveState on all iterators
Branch: master
https://github.com/mongodb/mongo/commit/ee2303939ee8cd88a5ff2ba78c0a67b69282891e

Comment by Githook User [ 21/Oct/14 ]

Author:

{u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}

Message: SERVER-15541 SERVER-15652 implement timing-based yielding
Branch: master
https://github.com/mongodb/mongo/commit/011dde7e6eac3b73cb1d2a7f004feee9bed99c46

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