Skip to content

Commit b4ee80f

Browse files
authored
DOCSP-44478-hardware-specs (#488)
* DOCSP-44478-hardware-specs * important note * JD feedback * ED feedback
1 parent f2c92ba commit b4ee80f

File tree

4 files changed

+38
-0
lines changed

4 files changed

+38
-0
lines changed

source/faq.txt

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -47,6 +47,22 @@ have to run on the servers that host your MongoDB instances. When
4747
(OS) that is different than the OS on the source or destination
4848
clusters.
4949

50+
What hardware specifications should the destination cluster have?
51+
-----------------------------------------------------------------
52+
53+
For most migrations, the destination cluster should have higher hardware
54+
specifications than the source cluster, including the following properties:
55+
56+
- CPU
57+
- Memory
58+
- Disk I/O
59+
60+
These hardware specifications ensure that the destination cluster can handle
61+
``mongosync`` writes and that the sync can keep up with the source cluster's
62+
workload.
63+
64+
.. include:: /includes/fact-oplog-disk-storage.rst
65+
5066
.. _c2c-faq-increase-oplog:
5167

5268
Should I increase the size of the ``oplog`` in the source cluster?
Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
The destination cluster must have enough disk storage to accommodate the logical
2+
data size being migrated and the destination oplog entries from the initial
3+
sync. For example, to migrate 10 GB of data, the destination cluster must have
4+
at least 10 GB available for the data and another 10 GB for the insert oplog
5+
entries from the initial sync.
6+
7+
To reduce the overhead of the destination oplog entries, you can:
8+
9+
- Use the :setting:`~replication.oplogSizeMB` setting to lower the destination
10+
cluster's oplog size.
11+
12+
- Use to :setting:`~storage.oplogMinRetentionHours` setting to lower or remove
13+
the destination cluster's minimum oplog retention period.

source/quickstart.txt

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -80,6 +80,10 @@ Setup
8080
The number of nodes in the destination replica set does not have
8181
to equal the number of nodes in the source replica set.
8282

83+
.. important::
84+
85+
.. include:: /includes/fact-oplog-disk-storage.rst
86+
8387
If your clusters are self-managed, they must be MongoDB
8488
Enterprise clusters. {+c2c-product-name+} is only supported on
8589
MongoDB Community Edition in a limited number of cases. For more

source/reference/oplog-sizing.txt

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,11 @@ be within the ``oplog`` time range.
2020

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

23+
Considerations
24+
--------------
25+
26+
.. include:: /includes/fact-oplog-disk-storage.rst
27+
2328
Monitor oplog Size Needed for Initial Sync
2429
------------------------------------------
2530

0 commit comments

Comments
 (0)