-
Type: Task
-
Resolution: Done
-
Priority: Critical - P2
-
Affects Version/s: None
-
Component/s: manual
-
Labels:
-
0.5
Description
Based on https://docs.mongodb.com/manual/tutorial/restore-sharded-cluster/.
Since the step includes dropping the local database of the config server (in effect, the oplog), it should also delete the _id: minOpTimeRecovery document in admin.system.version of every shard.
If the user decides to ever change the shardNames after restore, they would also need to drop config.cache.collections, config.cache.chunks.* (for v3.6 or greater) and drop config.cache.databases (for v4.0 or greater) in every shard.
Scope of changes
- (Pending feedback from engineering) add step for removing minOptimeRecovery document
- Add steps for removing various *.cache collections on shrad name change
- is duplicated by
-
DOCS-12347 Missing step to remove minOpTimeRecovery document during shared cluster restore
- Closed
- is related to
-
DOCS-9517 Docs for SERVER-24465: Remove recoverShardingState parameter
- Closed