[DOCS-14974] [Server] REP-32: Replicator: Basic Support for Sharded Clusters Created: 08/Dec/21  Updated: 13/Nov/23  Resolved: 15/Jul/22

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 1.0.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: Dave Cuthbert (Inactive)
Resolution: Fixed Votes: 0
Labels: c2c-ga-required
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
Duplicate
Participants:
Days since reply: 1 year, 32 weeks, 2 days ago
Epic Link: DOCSP-22764

 Description   
Downstream Change Summary

This project includes implementation that is depended on by REP-33.

Description of Linked Ticket

Epic Summary

Summary

Basic mongosync support for sharded clusters with like-like topologies

Motivation

As part of the Cluster to Cluster Replication Initiative, we will support replicating between two sharded clusters for both migration and continuous replication (disaster recovery) use cases. We will start with basic support for replicating between two sharded clusters with like-like topologies. This basic support does not include supporting concurrent chunk migrations, concurrent resharding, or changes in document shard key values on the source cluster during replication. Not having to worry about concurrent document move between source shards makes it an easier problem to solve. And this also allows us to create a foundation of sharded cluster support upon which REP-33 can be implemented.

Cast of Characters

  • Product Owner:
  • Project Lead:
  • Program Manager:

Documentation

Product Description
Scope Document
Technical Design Document



 Comments   
Comment by Lingzhi Deng [ 27/Jun/22 ]

REP-32 implemented how users would use multiple mongosync processes to replicate a sharded cluster.

Comment by Sarah Olson [ 25/May/22 ]

I added the mdb-world-required label to this and moved it to the 6.0 Upcoming epic, based on prioritization feedback from christopher.harris@mongodb.com. Please of course feel free to change it to one of the c2c epics as required. 

dave.cuthbert@mongodb.com, if this is a lot before World, it is fine to get to it shortly after MDBW as well. Please holler if you want help shuffling work! 

Comment by James Sanchez (Inactive) [ 08/Dec/21 ]

Hi melissa.mahoney this came through the capn queue. I am assigning this to you for triage because I think it is an Atlas ticket. Looks like feature work but I'm unclear from the linked docs and the description.

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