[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: |
|
||||||||||||
| 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: |
| 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: |