[DOCS-15702] [C2C] Investigate changes in REP-160: Support for Static Unlike Topologies Created: 25/Oct/22 Updated: 13/Nov/23 Resolved: 09/Jan/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | C2C, Server |
| Affects Version/s: | 1.1.0 |
| Fix Version/s: | 1.1.0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Kenneth Dyer |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | .local, nyc.local23 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Days since reply: | 1 year, 11 weeks, 1 day ago | ||||||||||||
| Epic Link: | DOCSP-26837 | ||||||||||||
| Description |
|
Original Downstream Change Summary We will need to update documentation to cover the new migration scenarios that are enabled Description of Linked TicketEpic Summary SummarySupport C2C sync between different cluster topologies on source and destination clusters MotivationCurrently, mongosync only supports replica set to replica set or N to N shards replication. This project allows for more flexibility in topologies and assists customers who want to scale in/out via C2C sync. For example, an on-prem customer managing a sharded cluster with a small number of shards may want to move to Atlas and scale out to a bigger sharded cluster at the same time. This project will enable use cases like that. Cast of Characters
DocumentationProduct Description |
| Comments |
| Comment by Frederic Vitzikam [ 22/Nov/22 ] | ||||||||||||
|
We added this section relatively late so the first section of the document was not updated to detail those changes, only reference back to that later section (I did fix the format example in the first section and re-read the text of the section for things that were no longer correct). Implementation ticket are https://jira.mongodb.org/browse/REP-1725 and https://jira.mongodb.org/browse/REP-1726. | ||||||||||||
| Comment by Frederic Vitzikam [ 09/Nov/22 ] | ||||||||||||
|
There were also some discussions in recent weeks about disabling the balancer. I updated the technical document to say that Mongosync does not touch the balancer so users are allowed to disable it if they want before the migration and can do so if they are worried about it impacting performances of the sync (even if we don't expect any issue at the moment, we also created a follow-up outside the project REP-1762). | ||||||||||||
| Comment by Frederic Vitzikam [ 03/Nov/22 ] | ||||||||||||
|
I saved the Slack conversation on [] vs {} for "key" in "sharding": [ {... "shardCollection": { "key": [] } } ] here. | ||||||||||||
| Comment by Frederic Vitzikam [ 02/Nov/22 ] | ||||||||||||
|
Edit (Dec 06, 2022): All the comments I made on this ticket are older than the document (Mongosync Downstream Changes) we are asked to fill now.
Note: there were some changes on "sharding" after this comment, see the following comments on the ticket. I only realized now that this ticket existed already, I was about to create documentation requests for REP-160. Since I already spent time gathering what I thought was worth cutting tickets for, I put what I had written below instead: As noted above we are adding support for unlike topologies (sharded cluster to replica set is out of scope for REP-160). We are also adding automatic pre-splitting of the destination cluster as part of this (there is a dedicated section in the technical design document linked above).
|