Loading...

XML

Word

Printable

JSON

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

Assigned Teams:

Query Optimization
Backwards Compatibility:
Minor Change
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

The RoutingContext shouldn't be terminated at the router - it must only be finished after it has validated the routing table by sending a versioned request to a shard. If the routing table version is stale for a shard, the shard will reject the request and inform the router that its information is stale, which will propagate up the call stack to the correct retry loops.

depends on

SERVER-102923 Introduce the RoutingContext API

Closed

is depended on by

SERVER-104020 Migrate scatterGatherVersionedTargetByRoutingTable functions to take in RoutingContext instead of CRI

Closed

related to

SERVER-104481 Add lightweight isSharded check that validates against a shard

Closed

SERVER-104469 Strengthen RoutingContext termination validation in test environments

Closed

Assignee:: Lynne Wang
Reporter:: Lynne Wang
Participants:: Githook User, Lynne Wang
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Mar 26 2025 05:53:32 PM UTC
Updated:: Apr 29 2025 06:23:59 PM UTC
Resolved:: Apr 17 2025 04:11:00 PM UTC
Confidence Status Last Update:: 08/Apr/25 9:05 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates