[DOCS-12743] Revise shardIdentity update instructions in Restore a Sharded Cluster Created: 22/May/19  Updated: 30/Oct/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: Eric Sedor Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-41202 admin.system.version is not restored ... Closed
Participants:
Days since reply: 19 weeks ago
Epic Link: DOCSP-1769

 Description   

Description

Regarding: https://docs.mongodb.com/manual/tutorial/restore-sharded-cluster/#optional-for-any-csrs-hostname-or-replica-set-name-changes-update-shard-metadata-in-each-shard-s-identity-document

Since TOOLS-481 prevents mongorestore from restoring system.version, the shardIdentity document won't exist on shards.

If this step is still necessary, could we change the suggested command to an insert and add language for getting the clusterId to the "important" section?

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Denis Iusupov [ 27/Sep/23 ]

It still actual

Comment by Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

Comment by Ravind Kumar (Inactive) [ 24/May/19 ]

OK - I'll test and see if there is a way to make this work given that.

Comment by Esha Maharishi (Inactive) [ 24/May/19 ]

> Hm. Unless there is an easy way for the user to get the clusterId , this feels kind of dead in the water. I'm not immediately aware of where users might find that value (possibly on the CSRS?)

I don't have any background about this ticket, but just a heads up that the clusterId can be found by querying the config server's config.version collection

Comment by Esha Maharishi (Inactive) [ 23/May/19 ]

ravind.kumar, the CSRS code to insert a shardIdentity document on a shard if the shard doesn't have it was removed in 3.6 development, since it was only intended to support the 3.2 -> 3.4 upgrade. :/

Generated at Thu Feb 08 08:05:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.