[SERVER-85280] changePrimary should fail if it encounters unexpectedly untracked collections Created: 17/Jan/24  Updated: 07/Feb/24

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Allison Easton Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: PM-3364-Milestone-5
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Catalog and Routing
Participants:

 Description   

After the track unsharded project completes, the only collections expected to be moved by changePrimary (using the movePrimary coordinator) are those that are client system namespaces. Any other collections should be tracked, and their presence indicates a problem in the sharding metadata.

If changePrimary encounters some untracked collection it does not expect, it should throw an error.


Generated at Thu Feb 08 06:57:20 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.