Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.2.0-rc0, 8.1.2, 8.0.13
Affects Version/s: None
Component/s: None
Labels:
- s8-required

Assigned Teams:

Server Programmability
Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v8.1, v8.0, v7.0
Sprint:
S8 Team 2025-05-26, N&O 2025-03-31, N&O 2025-04-14, N&O 2025-04-28, N&O 2025-05-12
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
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

SERVER-43618 taskExecutorPoolSize should be a startup only server parameter

Closed

is related to

SERVER-43618 taskExecutorPoolSize should be a startup only server parameter

Closed

SERVER-54504 Disable taskExecutorPoolSize for Linux

Closed

related to

SERVER-105377 Connection pre-warming only warms a single executor's pool

Backlog

split from

SERVER-102410 Investigate performance regressions on large sharded clusters with taskExecutorPoolSize=1

Open

Assignee:: Ryan Berryhill
Reporter:: Erin McNulty
Participants:: Erin McNulty, Githook User, Ryan Berryhill
Votes:: 0 Vote for this issue
Watchers:: 10 Start watching this issue

Created:: Mar 17 2025 06:11:13 PM UTC
Updated:: Jul 28 2025 09:00:42 PM UTC
Resolved:: Jun 03 2025 09:10:22 PM UTC
Confidence Status Last Update:: 22/May/25 6:37 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates