Skip to content

Commit e659f15

Browse files
committed
DOCS-12315: Fixup for restore sharded cluster proc
1 parent 82ee1d4 commit e659f15

File tree

1 file changed

+27
-10
lines changed

1 file changed

+27
-10
lines changed

source/includes/steps-restore-sharded-shard-primary-from-backup.yaml

Lines changed: 27 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -179,8 +179,23 @@ source:
179179
file: steps-restore-sharded-config-primary-from-backup.yaml
180180
ref: drop-local
181181
---
182-
title: "For any CSRS hostname or replica set name changes, update shard metadata in each shard's identity document."
182+
title: "Remove the ``minOpTimeRecovery`` document from the ``admin.system.versions`` collection."
183183
stepnum: 3
184+
ref: delete-minOpTimeRecovery
185+
content: |
186+
187+
Issue the following :method:`~db.collection.deleteOne()` method on the
188+
:data:`system.version <admin.system.version>` collection in the
189+
``admin`` database:
190+
191+
.. code-block:: javascript
192+
193+
use admin
194+
db.system.version.deleteOne( { _id: "minOpTimeRecovery" } )
195+
196+
---
197+
title: "For any CSRS hostname or replica set name changes, update shard metadata in each shard's identity document."
198+
stepnum: 4
184199
ref: metadata-update
185200
optional: true
186201
content: |
@@ -190,13 +205,15 @@ content: |
190205
* The hostnames for any CSRS host did not change during this procedure.
191206
* The CSRS replica set name did not change during this procedure.
192207
193-
Each shard has :data:`admin.system.versions` collection that
194-
contains metadata related to the shard, including the CSRS
195-
connection string. If either the CSRS name or any member hostnames
196-
changed while restoring the CSRS, you must update this metadata.
208+
The :data:`system.version <admin.system.version>`
209+
collection on the ``admin`` database contains metadata related
210+
to the shard, including the CSRS connection string. If either the
211+
CSRS name or any member hostnames changed while restoring the CSRS,
212+
you must update this metadata.
197213
198214
Issue the following :method:`~db.collection.find()` method on the
199-
:data:`~admin.system.versions` collection in the ``admin`` database:
215+
:data:`system.version <admin.system.version>` collection in the
216+
``admin`` database:
200217
201218
.. code-block:: javascript
202219
@@ -238,7 +255,7 @@ content: |
238255
CSRS metadata.
239256
240257
---
241-
stepnum: 4
258+
stepnum: 5
242259
ref: restart-as-repl
243260
source:
244261
file: steps-restore-sharded-config-primary-from-backup.yaml
@@ -254,13 +271,13 @@ replacement:
254271
clusterRole: shardsvr
255272
256273
---
257-
stepnum: 5
274+
stepnum: 6
258275
ref: initiate
259276
source:
260277
file: steps-restore-sharded-config-primary-from-backup.yaml
261278
ref: initiate
262279
---
263-
stepnum: 6
280+
stepnum: 7
264281
ref: add-members
265282
source:
266283
file: steps-restore-sharded-config-primary-from-backup.yaml
@@ -287,7 +304,7 @@ replacement:
287304
)
288305
component: "shard replica set"
289306
---
290-
stepnum: 7
307+
stepnum: 8
291308
ref: configure-replication
292309
source:
293310
file: steps-restore-sharded-config-primary-from-backup.yaml

0 commit comments

Comments
 (0)