|
| 1 | +:orphan: |
| 2 | + |
| 3 | +.. meta:: |
| 4 | + :robots: noindex, nosnippet |
| 5 | + |
| 6 | +.. _c2c-live-upgrade: |
| 7 | + |
| 8 | +============= |
| 9 | +Live Upgrades |
| 10 | +============= |
| 11 | + |
| 12 | +.. default-domain:: mongodb |
| 13 | + |
| 14 | +.. contents:: On this page |
| 15 | + :local: |
| 16 | + :backlinks: none |
| 17 | + :depth: 2 |
| 18 | + :class: singlecol |
| 19 | + |
| 20 | +.. important:: |
| 21 | + |
| 22 | + Starting in version 1.11.0, ``mongosync`` does not support live upgrades. To |
| 23 | + upgrade to the most recent version, see :ref:`c2c-release-version-numbers`. |
| 24 | + |
| 25 | + |
| 26 | +Starting in ``mongosync`` 1.7.0, you can live upgrade ``mongosync`` without |
| 27 | +restarting data synchronization operations from the beginning. |
| 28 | + |
| 29 | +After the live upgrade, ``mongosync`` continues operations that were in |
| 30 | +progress before the upgrade. |
| 31 | + |
| 32 | +To live upgrade ``mongosync``, perform these steps: |
| 33 | + |
| 34 | +.. procedure:: |
| 35 | + :style: normal |
| 36 | + |
| 37 | + .. step:: (Optional) Pause the ``mongosync`` processes |
| 38 | + |
| 39 | + To pause ``mongosync``, run :ref:`c2c-api-pause` on each running |
| 40 | + ``mongosync`` process. |
| 41 | + |
| 42 | + You can resume the ``mongosync`` processes later from the paused |
| 43 | + state, as shown in the final step. |
| 44 | + |
| 45 | + .. tip:: |
| 46 | + |
| 47 | + If you don't want to immediately resume data synchronization |
| 48 | + operations after live upgrade, consider pausing the |
| 49 | + ``mongosync`` processes. This is useful if you're coordinating |
| 50 | + operations from multiple ``mongosync`` processes. |
| 51 | + |
| 52 | + .. step:: Stop the ``mongosync`` processes |
| 53 | + |
| 54 | + Use your operating system to stop each running ``mongosync`` |
| 55 | + process. To stop a process, see your operating system |
| 56 | + documentation for the specific steps. |
| 57 | + |
| 58 | + .. step:: Download and install the new ``mongosync`` binaries |
| 59 | + |
| 60 | + To download and install the new ``mongosync`` binaries, see |
| 61 | + :ref:`download and install mongosync <c2c-install>`. |
| 62 | + |
| 63 | + .. step:: Initialize the ``mongosync`` processes |
| 64 | + |
| 65 | + To initialize the ``mongosync`` processes, see |
| 66 | + :ref:`Quickstart <c2c-quickstart>`. During initialization after a |
| 67 | + live upgrade, ``mongosync`` updates the persistent metadata. |
| 68 | + |
| 69 | + .. step:: Resume the ``mongosync`` processes |
| 70 | + |
| 71 | + If you paused any ``mongosync`` processes earlier in the optional |
| 72 | + first step, run :ref:`c2c-api-resume` on all ``mongosync`` |
| 73 | + processes. |
| 74 | + |
| 75 | +If a data synchronization operation was already in progress before the |
| 76 | +live upgrade, new features added in the latest ``mongosync`` version may |
| 77 | +not all be supported after the live upgrade. Performance improvements |
| 78 | +and bug fixes are always supported after the live upgrade. For more |
| 79 | +information on the new features that might be supported after a live |
| 80 | +upgrade, see the :ref:`1.7.0-c2c-release-notes`. |
0 commit comments