[DOCS-15881] Some missing info re: M -> N shard migrations Created: 07/Feb/23  Updated: 13/Nov/23  Resolved: 14/Feb/23

Status: Closed
Project: Documentation
Component/s: C2C, Server
Affects Version/s: None
Fix Version/s: 6.0.0, 6.1.0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Bug Priority: Major - P3
Reporter: Ryan Chipman Assignee: Dave Cuthbert (Inactive)
Resolution: Fixed Votes: 0
Labels: bugfix
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to DOCS-15702 [C2C] Investigate changes in REP-160:... Closed
is related to DOCS-15841 [C2C] mongosync quickstart still requ... Closed
Participants:
Days since reply: 1 year, 1 day ago

 Description   

Was recently discussing limitations of M->N shard migrations with kai.orend@mongodb.com, and we realized that the docs don't seem to note the prohibition on reversing a M->N shard migration (or, more generally, any unlike-topology migration).

Additionally, I noticed a tiny spot on this page that looks like it is out of date as of REP-160!

The source cluster and destination cluster must have the same number of shards.

cc tim.fogarty@mongodb.com as well for visibility


Generated at Thu Feb 08 08:14:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.