Skip to content

Commit faff914

Browse files
Review feedback
1 parent c268c0a commit faff914

File tree

1 file changed

+12
-2
lines changed

1 file changed

+12
-2
lines changed

source/faq.txt

Lines changed: 12 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,8 @@ Does ``mongosync`` have to use the same operating system as MongoDB Enterprise S
1515
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1616

1717
When ``mongosync`` runs on its own hardware, it does not have to use
18-
the same operation system (OS) as the source or destination clusters.
18+
the same operation system (OS) as the source or destination clusters it
19+
is connecting.
1920

2021
Should I increase the size of the oplog in the source cluster?
2122
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -27,7 +28,16 @@ of the replica set :term:`oplog` in the source cluster.
2728
The ``oplog`` in the source cluster must be large enough to track
2829
events that happen during the time it takes to complete the initial
2930
sync to the destination cluster.
30-
31+
32+
The proper ``oplog`` size depends on system hardware, network speed,
33+
and other factors including system workload. However, assuming network
34+
transfer speeds of 30-50GB per hour, a rough formula to estimate the
35+
required ``oplog`` size is:
36+
37+
.. code-block:: shell
38+
39+
minimumRetentionHours = dataSizeInGB / 30
40+
3141
To learn more about how to increase the size of the ``oplog``, see:
3242
:ref:`tutorial-change-oplog-size`.
3343

0 commit comments

Comments
 (0)