@@ -12,9 +12,7 @@ Release Notes for ``mongosync`` 1.4
12
12
:depth: 2
13
13
:class: singlecol
14
14
15
- .. note::
16
-
17
- ``mongosync`` 1.4 Released <<TBD>>, 2023
15
+ **Version 1.4 released June 16, 2023**
18
16
19
17
New Features
20
18
-------------
@@ -27,7 +25,73 @@ Starting in 1.4.0, you can set the workload level that
27
25
destination clusters. For more information, see the
28
26
:option:`--loadLevel` option.
29
27
28
+ Improved Resiliency for ``oplog`` Rollover
29
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
30
+
31
+ ``mongosync`` 1.4.0 improves :term:`oplog` handling. The ``oplog``
32
+ handling improvement adds resiliency to long running operations.
33
+
34
+ ``mongosync`` does an initial data copy and then applies updates from
35
+ the ``oplog`` to sync the source and destination clusters. In earlier
36
+ versions, ``mongosync`` waits to complete the initial sync before it
37
+ begins to replicate any changes from the ``oplog``. If there is a large
38
+ initial data set, the ``oplog`` can roll over before ``mongosync`` can
39
+ complete the initial data transfer. When this happens, the sync has to
40
+ be restarted from the beginning.
41
+
42
+ Starting in 1.4.0, ``mongosync`` begins to apply changes while the
43
+ initial sync is still in progress. Since ``mongosync`` starts to apply
44
+ changes earlier, ``mongosync`` maintains a recent position in the
45
+ ``oplog``. This mitigates the risk of ``oplog`` roll over and
46
+ significantly lowers the risk of restarting the sync.
47
+
48
+ For more information, see :ref:`oplog sizing <c2c-oplog-sizing>`.
49
+
50
+ Faster Processing
51
+ ~~~~~~~~~~~~~~~~~
52
+
53
+ Version 1.4.0 improves ``change event application`` speeds for improved
54
+ performance.
55
+
56
+ Improved Memory Handling
57
+ ~~~~~~~~~~~~~~~~~~~~~~~~
58
+
59
+ In version 1.4.0, ``mongosync`` uses less memory to buffer change
60
+ events. Improved memory handling alleviates some out-of-memory (OOM)
61
+ issues.
62
+
63
+ Telemetry
64
+ ~~~~~~~~~
65
+
66
+ Starting in 1.4.0, ``mongosync`` collects anonymous, aggregated usage
67
+ data to improve MongoDB products. You can disable collection of this
68
+ :ref:`telemetry <c2c-telemetry>` data when you start ``mongosync``.
69
+
70
+ Bug Fixes
71
+ ----------
72
+
73
+ - Fixes an issue so documents with ``_id`` values that evaluate to the
74
+ same string replicate correctly.
75
+
76
+ - Fixes a collection naming issue. Prior to version 1.4.0, ``mongosync``
77
+ crashes when a new collection reuses a dropped collection's name with
78
+ letter case changes.
79
+
80
+ For example, previous versions of ``mongosync`` crash if a new
81
+ ``SampleName`` collection replaces the dropped ``samplename``
82
+ collection.
83
+
84
+ Additional Considerations
85
+ -------------------------
86
+
87
+ The MongoDB server's :dbcommand:`validate` command may report data
88
+ corruption on destination clusters that run MongoDB version 6.0 through
89
+ 6.0.6. The data on the destination server is not corrupt. A bug in the
90
+ :ref:`WiredTiger <storage-wiredtiger>` database engine,
91
+ :issue:`WT-11051`, causes the false report.
92
+
30
93
Minimum Supported Version
31
94
-------------------------
32
95
33
96
In 1.4.0, the minimum supported version of MongoDB is 6.0.5.
97
+
0 commit comments