[SERVER-63102] Make separate internalQueryPlanEvaluationWorks knobs for the classic and SBE multi-planners Created: 28/Jan/22 Updated: 29/Oct/23 Resolved: 09/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0, 5.2.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | David Storch | Assignee: | David Storch |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | RDY | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Backport Requested: |
v5.2
|
||||||||||||||||||||||||
| Sprint: | QE 2022-02-21 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
The classic engine and SBE have completely different implementations of multi-planning (a.k.a. runtime plan selection). In In the same vein, we should separate internalQueryPlanEvaluationWorks into two knobs. Again, internalQueryPlanEvaluationWorks would be just for the classic engine and internalQueryPlanEvaluationWorksSbe would apply only to SBE. That way, if the default value of 10,000 for SBE proves to be too low, users or support engineers can increase its value without disturbing the behavior of queries using the classic engine. |
| Comments |
| Comment by Githook User [ 10/Feb/22 ] |
|
Author: {'name': 'David Storch', 'email': 'david.storch@mongodb.com', 'username': 'dstorch'}Message: The 'internalQueryPlanEvaluationWorks' parameter now only (cherry picked from commit a94caa502cf94fa6c8fcfea7283d7eaf3bd55ad5) |
| Comment by Githook User [ 09/Feb/22 ] |
|
Author: {'name': 'David Storch', 'email': 'david.storch@mongodb.com', 'username': 'dstorch'}Message: The 'internalQueryPlanEvaluationWorks' parameter now only |