This test verifies that the number of queries that each mongos or shardsvr mongod samples is proportional to the number of queries it routes. This is enforced via the sample rate assignment by the configsvr primary based on the traffic distribution information it has in memory. So the test doesn't pass reliably when there is continuous stepdown on the config server. It is unclear why it only starts failing a lot more very recently.
Disable sample_rates_sharded.js from the sharding_continuous_config_stepdown suite
- Votes:
-
0 Vote for this issue
- Watchers:
-
2 Start watching this issue
- Created:
- Updated:
- Resolved: