DOCSP-44478-hardware-specs #488
Conversation
✅ Deploy Preview for docs-cluster-to-cluster-sync ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
| The number of nodes in the destination replica set does not have | ||
| to equal the number of nodes in the source replica set. | ||
|
|
||
| .. important:: |
There was a problem hiding this comment.
for internal reviewer: Do you think there's a better way to format/include this information in this Quickstart section? Product specified that it'd be best here, but the way that the copy flows seems a bit clunky, and I can't really see a better way to format this section given it's within a procedure.
There was a problem hiding this comment.
I understand your concern, but I can't think of a better way to present it. The copy definitely is important and that placement makes sense to me even if it adds some visual noise due to multiple admonitions in the same step. I say go with it. Thanks!
jmd-mongo
left a comment
jmd-mongo
left a comment
There was a problem hiding this comment.
Thanks for this issue, @ajhuh-mdb! I left a suggestion and responded to your note re the admonition.
Thanks,
Joe
source/faq.txt
Outdated
| ``mongosync`` writes and that the sync can keep up with the source cluster's | ||
| workload. | ||
|
|
||
| Additionally, the destination cluster must have enough disk storage to |
There was a problem hiding this comment.
[suggestion]
Consider using includes/fact-oplog-disk-storage.rst here. I think the only difference would be the loss of "Additionally".
| The number of nodes in the destination replica set does not have | ||
| to equal the number of nodes in the source replica set. | ||
|
|
||
| .. important:: |
There was a problem hiding this comment.
I understand your concern, but I can't think of a better way to present it. The copy definitely is important and that placement makes sense to me even if it adds some visual noise due to multiple admonitions in the same step. I say go with it. Thanks!
|
Thanks for the initial review @jmd-mongo ! This should be ready for another pass. |
jmd-mongo
left a comment
jmd-mongo
left a comment
There was a problem hiding this comment.
Thanks for this updates, @ajhuh-mdb! This one LGTM at this point.
Thanks,
Joe
|
Hi @edobranov 👋 Whenever you get the chance, could you review this docs PR regarding hardware specifications for destination clusters? TIA! |
edobranov
left a comment
edobranov
left a comment
There was a problem hiding this comment.
LGTM % a couple optional suggestions, thanks!
| data size being migrated and the destination oplog entries from the initial | ||
| sync. For example, to migrate 10 GB of data, the destination cluster must have | ||
| at least 10 GB available for the data and another 10 GB for the insert oplog | ||
| entries. |
There was a problem hiding this comment.
| entries. | |
| entries from the initial sync. |
| To reduce the overhead of the destination oplog entries, you can: | ||
|
|
||
| - Use the :setting:`~replication.oplogSizeMB` setting to lower the destination | ||
| cluster's oplog size |
There was a problem hiding this comment.
| cluster's oplog size | |
| cluster's oplog size. |
* DOCSP-44478-hardware-specs * important note * JD feedback * ED feedback (cherry picked from commit b4ee80f)
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
* DOCSP-44478-hardware-specs * important note * JD feedback * ED feedback (cherry picked from commit b4ee80f)
3 participants
DESCRIPTION
STAGING
JIRA
https://jira.mongodb.org/browse/DOCSP-44478