Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.3.0-rc0
Affects Version/s: None
Component/s: None
Labels:
- bits-and-bobs-m1.4

Assigned Teams:

Query Integration
Backwards Compatibility:
Fully Compatible
CAR Domain/s:
None

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

See design doc tab IFR Flag Kick-back-and-retry. This ticket should probably aim to finish steps 4 and 5, and make a (noPassthrough?) test to show that a cluster with a router and a shard having different values of the feature flag will still result in predictable $vectorSearch results based on the router's feature flag value.

depends on

SERVER-115769 Add IncrementalFeatureRolloutContext::disableFlag()

Closed

SERVER-115770 Introduce IFRFlagRetryInfo and ErrorCodes::IFRFlagRetry

Closed

SERVER-116376 Extend query retry utils to allow for multiple error code retries

Closed

is depended on by

SERVER-115788 Gate extensions-in-subpipelines support behind featureFlagExtensionStageInSubpipeline

Closed

SERVER-116049 Implement IFRFlagRetry retry loop for $vectorSearch in subpipelines

Closed

related to

SERVER-116021 Give extensions ability to throw IFRFlagRetry to participate in IFR retry loop

Backlog

(1 related to)

Assignee:: Finley Lau
Reporter:: Will Buerger
Participants:: Finley Lau, Githook User, Will Buerger
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Dec 18 2025 10:06:56 PM UTC
Updated:: Jan 13 2026 05:29:18 AM UTC
Resolved:: Jan 13 2026 05:29:18 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates