[SERVER-24761] Queries being planned with the subplanner can ignore when the PlanExecutor is killed Created: 23/Jun/16  Updated: 17/Nov/16  Resolved: 14/Jul/16

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: 3.0.13, 3.2.9, 3.3.10

Type: Bug Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Max Hirschhorn
Resolution: Done Votes: 1
Labels: code-and-test
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-25039 Aggregation can attempt to re-plan af... Closed
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Completed:
Sprint: Query 17 (07/15/16), Query 18 (08/05/16)
Participants:
Linked BF Score: 0

 Description   

We still try to plan the query if planning for any of the subqueries returned an error status. This leads us to ignore the "PlanExecutor killed during plan selection" operation failed status that is returned by the MultiPlanStage and still try to build stages when the collection and indexes no longer exist.

// Use the multi plan stage to select a winning plan for each branch, and then construct
// the overall winning plan from the resulting index tags.
Status subplanSelectStat = choosePlanForSubqueries(yieldPolicy);
if (!subplanSelectStat.isOK()) {
    return choosePlanWholeQuery(yieldPolicy);
}



 Comments   
Comment by Githook User [ 15/Jul/16 ]

Author:

{u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'}

Message: SERVER-24761 Fix lint.

The trailing comma doesn't actually cause clang-format-3.6 to keep the
array elements on separate lines.
Branch: v3.2
https://github.com/mongodb/mongo/commit/8e6d244ffd81b72969c2a1931f0ddb3fb4ec2744

Comment by Githook User [ 15/Jul/16 ]

Author:

{u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'}

Message: SERVER-24761 Abort entire query plan when a catalog operation occurs.

Plan execution cannot proceed if the collection or a candidate index was
dropped during a yield. This prevents the subplanner from trying to
build plan stages when the collection and indexes no longer exist.

(cherry picked from commit a7e0e028e73c0b4f543c1ded1f4af0673630617a)
Branch: v3.0
https://github.com/mongodb/mongo/commit/3c1de5d668f3ebef750c6a4745d311d1b65bcbbc

Comment by Githook User [ 15/Jul/16 ]

Author:

{u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'}

Message: SERVER-24761 Abort entire query plan when a catalog operation occurs.

Plan execution cannot proceed if the collection or a candidate index was
dropped during a yield. This prevents the subplanner from trying to
build plan stages when the collection and indexes no longer exist.

(cherry picked from commit a7e0e028e73c0b4f543c1ded1f4af0673630617a)
Branch: v3.2
https://github.com/mongodb/mongo/commit/25c4706ca406196a76dc325b3836f5553148203f

Comment by Githook User [ 14/Jul/16 ]

Author:

{u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'}

Message: SERVER-24761 Abort entire query plan when a catalog operation occurs.

Plan execution cannot proceed if the collection or a candidate index was
dropped during a yield. This prevents the subplanner from trying to
build plan stages when the collection and indexes no longer exist.
Branch: master
https://github.com/mongodb/mongo/commit/a7e0e028e73c0b4f543c1ded1f4af0673630617a

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