Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Networking & Observability
Operating System:
ALL
Backport Requested:

v8.1, v8.0, v7.0
Sprint:
N&O 2025-03-31, N&O 2025-04-14
Confidence Status:
None

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

split from

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

Open

Assignee:: Joseph Prince

Reporter:: Erin McNulty

Participants:: Erin McNulty, Joseph Prince

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: Mar 17 2025 06:11:13 PM UTC

Updated:: Mar 31 2025 01:51:15 PM UTC

Confidence Status Last Update:: 24/Mar/25 11:05 PM

GA Target Date:: None

Public Preview Target Date:: None

Private Preview Target Date:: None

Experiment Target Date:: None

Details

Description

Attachments

Issue Links

Activity

People

Dates