Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 9.0.0-rc1
Affects Version/s: None
Component/s: None
Labels:
- shardedloadshedding9.0

Assigned Teams:

Cluster Scalability
Backwards Compatibility:
Fully Compatible
Sprint:
ClusterScalability 22Jun-6Jul
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

We need to test the error propagation behavior when a subset of requests in a scatter-gather query (both a regular find and an aggregation)
is rejected by the ingress operation rate limiter. We should cover both the budget exhaustion and retry cap scenarios.

related to

SERVER-130672 ingress_request_rate_limiter_maxtimems_backoff.js fails after SERVER-129657: overload retry counters now correctly report 0

Closed

SERVER-131303 Fix flaky retry-count assertion in ingress_request_rate_limiter_scatter_gather_error_propagation.js

Closed

SERVER-130225 Include per-shard info in mongos error response for scatter-gather find failures

Needs Scheduling

Assignee:: Anja Kalaba
Reporter:: Vojislav Stojkovic
Participants:: Anja Kalaba, Githook User, Vojislav Stojkovic
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: May 27 2026 02:16:29 AM UTC
Updated:: Jul 14 2026 07:08:32 AM UTC
Resolved:: Jul 02 2026 01:00:56 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates

PagerDuty