Loading...

XML

Word

Printable

JSON

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

Assigned Teams:

Catalog and Routing
Operating System:
ALL
Sprint:
CAR Team 2026-08-03
Linked BF Score:
200
Story Points:
2
CAR Domain/s:

🟦 Shard Catalog

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

The lookupCollectionBy* methods only consider commit-pending collections if the collection has been previously established via establishConsistentCollection.

This is a foot gun, and we should either fix it or document it in the header file. While SERVER-101457 will reduce the blast radius by making the lookupCollectionBy family only accessible inside the catalog, the problem still remains for internal usages. See ~~SERVER-104858~~ as an example.

causes

SERVER-130988 Initial sync collection cloner can permanently skip a collection that still exists on the sync source when NamespaceNotFound races with collection creation

In Code Review

is related to

SERVER-101457 Prevent layers above the catalog from directly accessing the internal CollectionCatalog

Blocked

related to

SERVER-122240 Fix internal callers of non-snapshot-aware CollectionCatalog listing methods

Backlog

SERVER-104858 acquireCollectionWithBucketsLookup does not use consistent collection snapshots

Closed

Assignee:: Yujin Kang Park
Reporter:: Josef Ahmad
Participants:: Josef Ahmad, Yujin Kang Park
Votes:: 0 Vote for this issue
Watchers:: 7 Start watching this issue

Created:: May 07 2025 08:06:35 AM UTC
Updated:: Jul 29 2026 08:52:22 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates

PagerDuty