-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Networking & Observability
-
ALL
-
v8.1, v8.0, v7.0
-
N&O 2025-03-31, N&O 2025-04-14, N&O 2025-04-28, N&O 2025-05-12
-
None
-
0
-
None
-
None
-
None
-
None
-
None
-
None
Broken out from SERVER-102410 to ensure we aren't blocking any customers from upgrading ASAP, though we'd still like to prioritize the work in SERVER-102410 to better understand the taskExecutorPoolSize parameter and why our assumptions about its correct value didn't hold up under a higher amount of load.
As part of this, lets also quickly check whether SERVER-43618 is still applicable, and ensure that customers cannot silently fail to tune the parameter at runtime.
- is duplicated by
-
-
- Closed
-
- is related to
-
-
- Closed
-
-
-
- Closed
-
- split from
-
-
- Open
-