[SERVER-83982] Filter through planCacheStats to ensure correct number of plans Created: 07/Dec/23 Updated: 13/Dec/23 Resolved: 13/Dec/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.3.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Adrian Gonzalez Montemayor | Assignee: | Adrian Gonzalez Montemayor |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Security 2023-12-11, Security 2023-12-25 | ||||
| Participants: | |||||
| Linked BF Score: | 5 | ||||
| Description |
|
In collection_plan_cache_stats.js we make several find queries and then count the number of plan cache entries. This can sometimes be flaky in some suites like replica_sets_initsync_jscore_passthrough because initSync will send queries than can be cached adding to the number of cached plans retireved. We should filter the planCacheStats to ensure we get the number of cached plans we care about. |