forked from mongodb/docs-cluster-to-cluster-sync
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathmigration-name.txt
65 lines (44 loc) · 1.4 KB
/
migration-name.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
.. _c2c-beta-migration-name:
=============
migrationName
=============
.. default-domain:: mongodb
.. contents:: On this page
:local:
:backlinks: none
:depth: 2
:class: singlecol
.. include:: /includes/beta-feature.rst
.. include:: /includes/migrationName.rst
Syntax
------
To set ``migrationName`` from the command line, use the ``--migrationName``
setting:
.. code-block:: shell
./bin/mongosync \
--cluster0 <connection-string> \
--cluster1 <connection-string> \
--migrationName <string>
To set ``migrationName`` in a :ref:`configuration file <c2c-config>`,
include the ``migrationName`` option:
.. code-block:: yaml
cluster0: <connection-string>
cluster1: <connection-string>
migrationName: <string>
Behavior
--------
The ``migrationName`` string can contain up to 44 alphanumeric and underscore
characters. ``migrationName`` is appended to the string
``"mongosync_internal_"`` to set the migration metadata database name.
For example, if you set ``migrationName`` to
``"cluster_27000_to_cluster_35000_sync"``, the resulting ``mongosync`` metadata
database name is ``"mongosync_internal_cluster_27000_to_cluster_35000_sync"``.
.. _c2c-beta-multiple-migration-examples:
Examples
--------
To view examples that use ``migrationName``, see:
- :ref:`c2c-beta-abc-migration`
- :ref:`c2c-beta-many-to-one`
Learn More
----------
- :ref:`c2c-beta-program`