Loading...

XML

Word

Printable

JSON

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

Assigned Teams:

Query Integration
Confidence Status:
None
Work Order:
0

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

This is the first step of enforcing the contract that a RoutingContext used for a routing operation can only be safely destructed if it has its routing tables validated by sending a versioned request to a shard.

The following functions will be migrated over to the RoutingContext:

scatterGatherVersionedTargetByRoutingTable
scatterGatherVersionedTargetByRoutingTableNoThrowOnStaleShardVersionErrors

Any code that calls into these functions must acquire their routing tables through. the RoutingContext instead of directly accessing the CatalogCache.

depends on

SERVER-102928 Validate the RoutingContext before termination

Closed

SERVER-104175 Remove redundant dbName parameter from scatterGather functions

Closed

is duplicated by

SERVER-102926 Replace direct CatalogCache accesses in the sharded query command code with the RoutingContext

Closed

is related to

SERVER-104175 Remove redundant dbName parameter from scatterGather functions

Closed

related to

SERVER-104347 Remove isSharded() check in SessionsCollectionConfigServer::_generateIndexesIfNeeded()

Backlog

SERVER-102926 Replace direct CatalogCache accesses in the sharded query command code with the RoutingContext

Closed

SERVER-104175 Remove redundant dbName parameter from scatterGather functions

Closed

(2 related to)

Assignee:: Lynne Wang

Reporter:: Lynne Wang

Participants:: Lynne Wang

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: Apr 18 2025 07:00:45 PM UTC

Updated:: Apr 25 2025 03:32:39 PM UTC

Confidence Status Last Update:: 18/Apr/25 7:01 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates