This repository was archived by the owner on May 1, 2025. It is now read-only.
File tree Expand file tree Collapse file tree 2 files changed +5
-10
lines changed Expand file tree Collapse file tree 2 files changed +5
-10
lines changed Original file line number Diff line number Diff line change
1
+ To reverse sync, the user must have assigned the :authrole: `restore `
2
+ role for both source and destination and the ``enableUserWriteBlocking ``
3
+ field must be set to ``sourceAndDestination ``.
Original file line number Diff line number Diff line change @@ -141,11 +141,7 @@ Request Body Parameters
141
141
cluster while migration is in progress, and unblocks writes right
142
142
before ``canWrite`` is ``true``.
143
143
144
- .. include:: /includes/fact-permissions-body.rst
145
-
146
- To reverse sync, the user must have assigned the :authrole:`restore`
147
- role for both source and destination and the ``enableUserWriteBlocking``
148
- field must be set to ``"sourceAndDestination"``.
144
+ .. include:: /includes/api/facts/reverse-sync.rst
149
145
150
146
To allow the source cluster to accept writes again, for example
151
147
after running migration tests, run the following command:
@@ -179,12 +175,8 @@ Request Body Parameters
179
175
- Optional
180
176
- If set to ``true``, enables the sync operation to be
181
177
reversed.
182
-
183
- .. include:: /includes/fact-permissions-body.rst
184
178
185
- To reverse sync, the user must have assigned the :authrole:`restore`
186
- role for both source and destination and the ``enableUserWriteBlocking``
187
- field must be set to ``sourceAndDestination``.
179
+ .. include:: /includes/api/facts/reverse-sync.rst
188
180
189
181
This option is not supported for the following configurations:
190
182
You can’t perform that action at this time.
0 commit comments