Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.2.0-rc0
Affects Version/s: None
Component/s: None
Labels:

Assigned Teams:

Networking & Observability
Backwards Compatibility:
Fully Compatible
Sprint:
N&O 2025-04-28, N&O 2025-05-12, N&O 2025-05-26, N&O 2025-06-09
Case:
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

In the event that the number of connection acquisition requests vastly outnumbers the maximum size of a pool, it's possible for the pool to get stuck thrashing between pushing new requests on the queue and popping older ones off when they time out, rather than making any progress towards actually servicing requests. We should consider outright rejecting work when the queue reaches a certain length, possibly as a factor of the maximum size (e.g. 1,000x the pool size).

is related to

SERVER-96848 Reject work if reactor is overwhelmed

Backlog

SERVER-96811 Use ThreadPool in ReplicaSetMonitor-TaskExecutor

Closed

SERVER-104141 Support attaching error labels to arbitrary Statuses

Closed

SERVER-105744 Use code other than TemporarilyUnavailable for ConnectionPool request rejection

Closed

Assignee:: Michael Popov
Reporter:: Patrick Freed
Participants:: Githook User, Michael Popov, Patrick Freed
Votes:: 0 Vote for this issue
Watchers:: 14 Start watching this issue

Created:: Jun 13 2024 02:50:03 PM UTC
Updated:: Jul 22 2025 12:52:56 AM UTC
Resolved:: Jun 03 2025 10:03:03 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates