[SERVER-83777] Cap $in length in plan cache key with internalQueryMaxScansToExplode + 1 Created: 01/Dec/23 Updated: 02/Jan/24 Resolved: 04/Dec/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.1, 7.3.0-rc0, 7.0.5 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ivan Fefer | Assignee: | Ivan Fefer |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Backport Requested: |
v7.2, v7.0
|
||||||||||||||||
| Sprint: | QE 2023-12-11 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 35 | ||||||||||||||||
| Description |
|
The reason we add $in length to plan cache key is possible explodeForSort optimization. We have internalQueryMaxScansToExplode query knob that limits the maximum number of explode for sort index scans. We can use it to limit the number of plan cache entries. |
| Comments |
| Comment by Githook User [ 29/Dec/23 ] |
|
Author: {'name': 'Ivan Fefer', 'email': 'ivan.fefer@mongodb.com', 'username': 'Fefer-Ivan'}Message: |
| Comment by Githook User [ 06/Dec/23 ] |
|
Author: {'name': 'Ivan Fefer', 'email': 'ivan.fefer@mongodb.com', 'username': 'Fefer-Ivan'}Message: GitOrigin-RevId: 2d78af0dade10b3ba01713ad3e24f41c23674ca5 |
| Comment by Githook User [ 04/Dec/23 ] |
|
Author: {'name': 'Ivan Fefer', 'email': 'ivan.fefer@mongodb.com', 'username': 'Fefer-Ivan'}Message: GitOrigin-RevId: d314c222ea10217d45f199f84a037cbf493065ff |
| Comment by David Storch [ 01/Dec/23 ] |
|
Requesting backport to 7.2 in addition to 7.0. |