Loading...

XML

Word

Printable

JSON

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

Assigned Teams:

Catalog and Routing
Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
CAR Team 2025-02-17, CAR Team 2025-03-03, CAR Team 2025-03-17, CAR Team 2025-08-04, CAR Team 2025-08-18, CAR Team 2025-09-01
CAR Domain/s:

🟦 Shard Catalog

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

Currently, when we add a replica set to a sharded cluster using the addShard command, and that replica set contains data, we manually register the collection in the global catalog by writing to config.databases.

In the context of SPM-3729, this process bypasses registration in the shard-local catalog, which makes the shards not being authoritative for databases.

depends on

SERVER-100447 Temporary ban tests that add a replica set with existing dbs in a sharded cluster

Closed

is depended on by

SERVER-88639 Enable feature flag for SPM-3729

Blocked

related to

SERVER-80532 Sharding catalog may be missing databases created via direct connections during/after addShard

Backlog

SERVER-104385 Update the addShard coordinator to detect the promotion to sharded case

Closed

Assignee:: Wolfee Farkas
Reporter:: Pol Pinol
Participants:: Githook User, Pol Pinol, Wolfee Farkas
Votes:: 0 Vote for this issue
Watchers:: 6 Start watching this issue

Created:: Feb 04 2025 04:10:22 PM UTC
Updated:: Sep 01 2025 08:26:02 AM UTC
Resolved:: Aug 26 2025 12:24:07 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates