-
Notifications
You must be signed in to change notification settings - Fork 39
DOCSP-45117-sharded-cluster-behavior #472
Conversation
✅ Deploy Preview for docs-cluster-to-cluster-sync ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ltran-mdb2 LGTM with suggestions. Cheers.
|
||
Running :dbcommand:`movePrimary` on the source or desintation cluster | ||
during migration may result in a fatal error or require you to | ||
restart the migration from scratch. For more information, see |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider: "from the start"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
Primary Shards | ||
`````````````` | ||
|
||
When ``mongosync`` syncs to a sharded destination cluster, it assigns a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider clarifying what "it assigns" refers to. Cheers.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
Even if documents move between source shards during replication, | ||
{+c2c-product-name+} maintains the :term:`eventual consistency` | ||
guarantee on the destination cluster. For more information, see | ||
:ref:`c2c-sharded-clusters`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I mentioned in the description of DOCSP-45117 that the balancer / chunk migration stuff no longer applies, so L62- L71 isn't relevant anymore. We can instead 'summarize' the two sub-sections after it by replacing L62 - L71 with:
{+c2c-product-name+} supports replication between sharded clusters. Individual shards are replicated in parallel from the source cluster to the destination cluster, however the source cluster's sharding configuration is not preserved.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thank you!
* DOCSP-45117-sharded-cluster-behavior * DOCSP-45117-sharded-cluster-behavior * DOCSP-45117 fixing label * DOCSP-45117 copy edits * DOCSP-45117 tech edit * DOCSP-45117 fixing underline (cherry picked from commit 0ab11b3)
* DOCSP-45117-sharded-cluster-behavior * DOCSP-45117-sharded-cluster-behavior * DOCSP-45117 fixing label * DOCSP-45117 copy edits * DOCSP-45117 tech edit * DOCSP-45117 fixing underline (cherry picked from commit 0ab11b3) # Conflicts: # source/reference/api/start.txt
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
* DOCSP-45117-sharded-cluster-behavior * DOCSP-45117-sharded-cluster-behavior * DOCSP-45117 fixing label * DOCSP-45117 copy edits * DOCSP-45117 tech edit * DOCSP-45117 fixing underline (cherry picked from commit 0ab11b3) # Conflicts: # source/reference/api/start.txt
DESCRIPTION
Adds info on shared cluster behavior and moves sections to the general mongosync behavior page
STAGING
https://deploy-preview-472--docs-cluster-to-cluster-sync.netlify.app/reference/mongosync/mongosync-behavior/#sharded-clusters
https://deploy-preview-472--docs-cluster-to-cluster-sync.netlify.app/reference/api/start/#behavior
JIRA
https://jira.mongodb.org/browse/DOCSP-45117
SELF-REVIEW CHECKLIST
See the taxonomy tagging instructions and this example PR
EXTERNAL REVIEW REQUIREMENTS
What's expected of an external reviewer?