File tree Expand file tree Collapse file tree 1 file changed +12
-2
lines changed Expand file tree Collapse file tree 1 file changed +12
-2
lines changed Original file line number Diff line number Diff line change @@ -15,7 +15,8 @@ Does ``mongosync`` have to use the same operating system as MongoDB Enterprise S
15
15
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
16
16
17
17
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.
19
20
20
21
Should I increase the size of the oplog in the source cluster?
21
22
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -27,7 +28,16 @@ of the replica set :term:`oplog` in the source cluster.
27
28
The ``oplog`` in the source cluster must be large enough to track
28
29
events that happen during the time it takes to complete the initial
29
30
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
+
31
41
To learn more about how to increase the size of the ``oplog``, see:
32
42
:ref:`tutorial-change-oplog-size`.
33
43
You can’t perform that action at this time.
0 commit comments