-
Type: Bug
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Server Security
-
ALL
-
Sharding EMEA 2023-06-26, Sharding EMEA 2023-07-24, Sharding EMEA 2023-08-07, Sharding EMEA 2023-08-21, Sharding EMEA 2023-10-16
-
5
-
2
As the fresh_mongos case does not wait for stable performance, this test can be heavily thrown off whenever new startup tasks are added (see linked BF for an example of a change in a startup task causing a regression due to timing overlap with this test). Having a wider tolerance for such cases, reworking this case, or removing it could all be plausible solutions.
- is duplicated by
-
SERVER-78528 Background threads in mongos cause mongos_large_catalog_workloads test case to measure performance incorrectly
- Closed
- is related to
-
SERVER-78528 Background threads in mongos cause mongos_large_catalog_workloads test case to measure performance incorrectly
- Closed