[DOCS-9379] Comment on: "manual/tutorial/restore-sharded-cluster.txt" Created: 25/Nov/16 Updated: 30/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Alan K Ho | Assignee: | Ravind Kumar (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | collector-298ba4e7, sharding | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
MongoS version 3.2.10, 64-bit OSX 10.11.6 Location: https://docs.mongodb.com/manual/tutorial/restore-sharded-cluster/#restore-sh-cl-dmp |
||
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 2 days ago |
| Epic Link: | DOCSP-1769 |
| Story Points: | 2.5 |
| Description |
|
Following this guide, when I got to step 9 I needed to update the hostname for the new shard. However, following Step 8 and Step 9 here didn't quite work and I kept getting error that said mongodb couldn't reach the new shard host. mongos> show dbs I am using mongodb 3.2.10 After doing this a few times, I realized that updating shard hostnames should be done after Step 7, before starting any mongos instances (Step 8). This means that one must update the hostname in the config database by connecting to CSRS Config Server Primary. I performed this workaround and my sharded cluster finally restored correctly. I would also recommend maybe you could provide an quick example of code snippet on how to change the hostname in the config database for shards, as described below: cfgServer> use config , {$set:{"host": <newShardName>/CSRS server list and ports> }}) Thanks! |
| Comments |
| 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! |