-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Optimization
-
ALL
-
v8.3
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
In SERVER-87466, a refactor to replanning was made to reuse top-level planning logic in case a cached plan was inefficient. Since the old replanning path would never create a subplanner, logic was added to the new path to match this behavior. This keeps behavior consistent and is less risky for 8.3
As part of SERVER-120958, the logic to prevent a subplanner from being created during replanning may have accidentally been removed. In the repro below, we see that a plan is cached, then replanned when many more documents are inserted, and we reach a tassert because the replanning path created a subplanner
- is related to
-
SERVER-121873 Create new repeat_queries passthrough where replanning always occurs
-
- In Progress
-
-
SERVER-120958 Remove automatic subplanner
-
- Closed
-
-
SERVER-87466 Trigger replanning by throwing an exception, instead of creating another planner
-
- Closed
-