-
Notifications
You must be signed in to change notification settings - Fork 39
DOCSP-45860-older-version-limitations #522
Changes from all commits
f502fd9
9dde24c
4534750
a7cf0c1
8fe1509
f680282
555b02d
12064cf
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,46 @@ | ||
- Writes that produce :term:`DDL <DDL (Data Definition Language)>` events cannot | ||
occur on the source cluster during the migration. The following events cannot | ||
occur: | ||
|
||
- ``collMod`` | ||
- ``create`` | ||
- ``createIndexes`` | ||
- ``drop`` | ||
- ``dropDatabase`` | ||
- ``dropIndexes`` | ||
- ``refineCollectionShardKey`` | ||
- ``rename`` | ||
- ``reshardCollection`` | ||
- ``shardCollection`` | ||
|
||
This includes operations that may create new collections such as | ||
:dbcommand:`mapReduce`, :pipeline:`$out`, and :pipeline:`$merge`. This also | ||
includes collections created implicitly from inserts. Only writes that produce | ||
CRUD events can occur during the migration. | ||
|
||
.. note:: | ||
|
||
Writes that produce DDL events on source collections outside of the | ||
:ref:`namespace filter <c2c-filtered-sync>` are allowed. | ||
|
||
- ``geoHaystack`` indexes are not supported. | ||
|
||
- :ref:`/reverse <c2c-api-reverse>` endpoint is not supported. You can't | ||
enable the ``reversible`` option in the :ref:`/start <c2c-api-start>` request. | ||
|
||
- You can't enable the ``enableUserWriteBlocking`` option in the ``/start`` | ||
request. Ensure that no writes are made to the source or destination cluster | ||
during the migration. | ||
|
||
- You can't enable the ``createSupportingIndexes`` :ref:`sharding parameter | ||
<c2c-api-start-sharding>`. Instead, create an index to support your shard key | ||
on the source cluster. | ||
|
||
- If there are any indexes with inconsistent specs or that are missing | ||
``mongosync`` returns an error. To check for index inconsistencies, see | ||
:ref:`manage-indexes-find-inconsistent-indexes`. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @ajayvijayakumar123 is this a change from status quo mongosync GA? We have 'mongosync only syncs indexes that have consistent index specifications on all shards.' in the limitations today There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yup. For 6.0+ migrations, mongosync ignores inconsistent indexes and just doesn't build them on the destination. For pre-6.0 migrations, mongosync will error on these indexes. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'll make it clear that it'll error on pre-6.0 migrations There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. thanks! |
||
|
||
- For source clusters running MongoDB 4.4, :ref:`SRV connection strings | ||
<connections-dns-seedlist>` are not supported. You must use a | ||
:ref:`standard connection string | ||
<connections-standard-connection-string-format>`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we add a note here that the user is responsible for preventing writes to the source or destination?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mvankeulen94 @ajayvijayakumar123 do we have a way of ensuring users don't write to their clusters without the
enableUserWriteBlocking
option? Or is this something they just need to manually make sure of?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think they just need to manually make sure