[DOCS-15629] Make mongosync limitations more prominent Created: 14/Sep/22  Updated: 30/Oct/23  Resolved: 29/Sep/23

Status: Closed
Project: Documentation
Component/s: C2C
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Critical - P2
Reporter: Kevin Adistambha Assignee: Lauren Tran
Resolution: Done Votes: 0
Labels: server-docs-bug-bash
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 1 year, 21 weeks, 1 day ago
Epic Link: DOCSP-22764

 Description   

Due to some confusion in the community (e.g. https://www.mongodb.com/community/forums/t/how-mongosync-can-be-done-if-i-want-to-sync-two-m0primary-atlas-clusters-which-are-of-mongo-5-0-12/186353), it will be great if the limitations of mongosync can be made a lot more prominent, such as:

  • Not supporting Atlas shared tier, and
  • Not supporting Serverless instances.

This is actually mentioned in the mongosync limitations page (https://www.mongodb.com/docs/cluster-to-cluster-sync/current/reference/limitations/), but currently there is no easy way to get to this page, other than using the navbar on the left.


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