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
Sprint:
CAR Team 2025-03-31
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

Magic restore supports selective restore of collections. When performing such a restore in a sharded cluster, it will send a _configsvrRunRestore to the config server to remove metadata of non restored collections. Since now shards store metadata authoritatively, we need to send a similar command also to shards.

depends on

SERVER-68747 Drop databases during a selective restore if no collections in the database were restored

Backlog

related to

SERVER-100083 Refine _configsvrRunRestore to Include Database Metadata Collections on Config Shards

Closed

SERVER-99799 Consider adding `config.shard.databases` to the magic restore procedure

Closed

Assignee:: Unassigned
Reporter:: Aitor Esteve Alvarado
Participants:: Aitor Esteve Alvarado
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Mar 17 2025 02:50:44 PM UTC
Updated:: Apr 02 2025 02:59:12 PM UTC
Confidence Status Last Update:: 20/Mar/25 3:11 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates