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:

Catalog and Routing
Story Points:
2
Confidence Status:
None
Work Order:
3
Size Category:
TBD
CAR Domain/s:

🟥 DDL

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

This "isSharded" check is redundant: _generateIndexesIfNeeded is only ever called after _shardCollectionIfNeeded, which should have sharded the collection. Although this node's CatalogCache might now be stale, whenever it later dispatches the createIndexes cmd the shard will reject the request and inform the router that it is stale. It can be safely removed.

is related to

SERVER-57519 Make ARS use causally consistent ShardRegistry::getShard() function

Closed

SERVER-61214 Ensure having the latest known entry of the catalog cache when creating config.system.sessions

Closed

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

Closed

related to

SERVER-61214 Ensure having the latest known entry of the catalog cache when creating config.system.sessions

Closed

Assignee:: Paolo Polato
Reporter:: Lynne Wang
Participants:: Lynne Wang, Paolo Polato
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Apr 25 2025 03:32:24 PM UTC
Updated:: Aug 01 2025 01:21:45 PM UTC
Confidence Status Last Update:: 01/Aug/25 10:00 AM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates