Skip to content
This repository was archived by the owner on May 1, 2025. It is now read-only.

DOCSP-44478-hardware-specs #488

Merged
ajhuh-mdb merged 4 commits into from
Nov 15, 2024
Merged

DOCSP-44478-hardware-specs #488

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
692ca4e
DOCSP-44478-hardware-specs
ajhuh-mdb Nov 14, 2024
1b43450
important note
ajhuh-mdb Nov 14, 2024
e7744e0
JD feedback
ajhuh-mdb Nov 15, 2024
99821cc
ED feedback
ajhuh-mdb Nov 15, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions source/faq.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,6 +47,22 @@ have to run on the servers that host your MongoDB instances. When
(OS) that is different than the OS on the source or destination
clusters.

What hardware specifications should the destination cluster have?
-----------------------------------------------------------------

For most migrations, the destination cluster should have higher hardware
specifications than the source cluster, including the following properties:

- CPU
- Memory
- Disk I/O

These hardware specifications ensure that the destination cluster can handle
``mongosync`` writes and that the sync can keep up with the source cluster's
workload.

.. include:: /includes/fact-oplog-disk-storage.rst

.. _c2c-faq-increase-oplog:

Should I increase the size of the ``oplog`` in the source cluster?
Expand Down
13 changes: 13 additions & 0 deletions source/includes/fact-oplog-disk-storage.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
The destination cluster must have enough disk storage to accommodate the logical
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 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.

- Use to :setting:`~storage.oplogMinRetentionHours` setting to lower or remove
the destination cluster's minimum oplog retention period.
4 changes: 4 additions & 0 deletions source/quickstart.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -80,6 +80,10 @@ Setup
The number of nodes in the destination replica set does not have
to equal the number of nodes in the source replica set.

.. important::
Copy link
Collaborator Author

@ajhuh-mdb ajhuh-mdb Nov 14, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Collaborator

@jmd-mongo jmd-mongo Nov 14, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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!

Copy link
Collaborator Author

@ajhuh-mdb ajhuh-mdb Nov 15, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gotcha, thanks!


.. include:: /includes/fact-oplog-disk-storage.rst

If your clusters are self-managed, they must be MongoDB
Enterprise clusters. {+c2c-product-name+} is only supported on
MongoDB Community Edition in a limited number of cases. For more
Expand Down
5 changes: 5 additions & 0 deletions source/reference/oplog-sizing.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,11 @@ be within the ``oplog`` time range.

.. include:: /includes/fact-oplog-background

Considerations
--------------

.. include:: /includes/fact-oplog-disk-storage.rst

Monitor oplog Size Needed for Initial Sync
------------------------------------------

Expand Down