@@ -58,79 +58,10 @@ released, version 2.0 would no longer receive patch releases. At the
5858same time, version 1.3 would continue to receive patches until version
59591.4 was released.
6060
61- .. _c2c-versioning-live-upgrade:
61+ Upgrade or Downgrade
62+ ~~~~~~~~~~~~~~~~~~~~
6263
63- Live Upgrade
64- ~~~~~~~~~~~~
65-
66- .. versionadded:: 1.7.0
67-
68- Starting in ``mongosync`` 1.7.0, you can upgrade ``mongosync`` without
69- restarting data synchronization operations from the beginning.
70-
71- .. important::
72-
73- ``mongosync`` does not support live upgrades to version 1.11.
74-
75- After the live upgrade, ``mongosync`` continues operations that were in
76- progress before the upgrade.
77-
78- To live upgrade ``mongosync``, perform these steps:
79-
80- .. procedure::
81- :style: normal
82-
83- .. step:: (Optional) Pause the ``mongosync`` processes
84-
85- To pause ``mongosync``, run :ref:`c2c-api-pause` on each running
86- ``mongosync`` process.
87-
88- You can resume the ``mongosync`` processes later from the paused
89- state, as shown in the final step.
90-
91- .. tip::
92-
93- If you don't want to immediately resume data synchronization
94- operations after live upgrade, consider pausing the
95- ``mongosync`` processes. This is useful if you're coordinating
96- operations from multiple ``mongosync`` processes.
97-
98- .. step:: Stop the ``mongosync`` processes
99-
100- Use your operating system to stop each running ``mongosync``
101- process. To stop a process, see your operating system
102- documentation for the specific steps.
103-
104- .. step:: Download and install the new ``mongosync`` binaries
105-
106- To download and install the new ``mongosync`` binaries, see
107- :ref:`download and install mongosync <c2c-install>`.
108-
109- .. step:: Initialize the ``mongosync`` processes
110-
111- To initialize the ``mongosync`` processes, see
112- :ref:`Quickstart <c2c-quickstart>`. During initialization after a
113- live upgrade, ``mongosync`` updates the persistent metadata.
114-
115- .. step:: Resume the ``mongosync`` processes
116-
117- If you paused any ``mongosync`` processes earlier in the optional
118- first step, run :ref:`c2c-api-resume` on all ``mongosync``
119- processes.
120-
121- If a data synchronization operation was already in progress before the
122- live upgrade, new features added in the latest ``mongosync`` version may
123- not all be supported after the live upgrade. Performance improvements
124- and bug fixes are always supported after the live upgrade. For more
125- information on the new features that might be supported after a live
126- upgrade, see the :ref:`1.7.0-c2c-release-notes`.
127-
128- Non-Live Upgrade or Downgrade
129- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
130-
131- If you're using an earlier ``mongosync`` version not supported by the
132- live upgrade procedure, or you need to downgrade ``mongosync``, perform
133- these steps:
64+ To upgrade or downgrade ``mongosync``, perform these steps:
13465
13566- Stop all currently running ``mongosync`` processes.
13667- Drop all non-system databases in the destination cluster.
0 commit comments