[DOCS-14983] Investigate changes in REP-30: Replicator: Support Reversing Direction of Replication Created: 10/Dec/21  Updated: 13/Nov/23  Resolved: 14/Jun/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: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
Participants:
Days since reply: 2 years, 8 weeks, 5 days ago
Epic Link: DOCSP-22764

 Description   
Downstream Change Summary

This project will add CLI options to the mongosync replicator. In particular, it will add a "commit" command to ensure the source and destination cluster are consistent with each other, and a command to control the direction of replication.

As the project is in early stages, this summary will be updated with more downstream impacts as the project progresses. Thanks!

Description of Linked Ticket

Epic Summary

Summary

Support reversing the direction of replication after a healthy cutover period

Motivation

While replicating data between two clusters, customers sometimes want the ability to swap roles between source and destination clusters - enabling them to switch their applications/business workflows back to the source cluster if they discover issues (data integrity, performance, other issues).

Cast of Characters

  • Product Owner: Alan Zheng
  • Project Lead: Ali Mir
  • Program Manager: Elizabeth Roytburd

Documentation

Product Description
Scope Document
Technical Design Document


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