Currently, plan_cache_stats_shard_and_host.js compares number of shards for a collection to the total number of plan cache entries. This fails if we have additional cache entries due to queries run on the collection in the background. To address this issue, we should compare the number of shards in a collection with the number of plan cache entries that correspond specifically to the query's planCacheKey tested by the script.
Robustify plan_cache_stats_shard_and_host.js to count plan cache entries only for specific plan cache key
- Votes:
-
0 Vote for this issue
- Watchers:
-
2 Start watching this issue
- Created:
- Updated:
- Resolved: