As discovered in BF-28888, in suites with stepdown/kill/terminate or chunk migration, read and write queries are bound to get interrupted and retried; and when retries occur a lot, the actual query patterns would be very different from the intended query patterns and consequently the metrics would fall outside of the windows allowed by the metrics check.
Make analyze_shard_key.js concurrency workload only validate read and write distribution metrics if the sample population matches the mock query patterns
- Votes:
-
0 Vote for this issue
- Watchers:
-
2 Start watching this issue
- Created:
- Updated:
- Resolved: